WebMCP tool community integration
Risk level
medium
40/100

Latch ↗

Latch is a community-maintained WebMCP tool from Latch. Anomity scores its risk at 40 out of 100 (medium).

browser:control network:outbound

Analysis summary

Latch is a community-maintained WebMCP tool from Latch. Anomity scores its risk at 40 out of 100 (medium).

Latch is a one-script WebMCP integration for existing sites. Rather than asking developers to hand-author tool definitions, it inspects the page for recognisable search handlers, cart actions, and form submissions and automatically registers matching WebMCP tools. The pitch is agent-readiness without a rewrite.

Automatic registration is the risk. A hand-written tool surface is a deliberate list of what agents may do; an inferred one is whatever the scanner happened to recognise, which can include destructive form handlers nobody intended to publish. Latch declares browser control and outbound network access. If you deploy it, audit the resulting tool list the way you would audit a newly generated API — with the Inspector or Radar — before assuming the surface matches your intent.

Why this entry scored 40 out of 100

This profile starts at the catalog's neutral base of 50. Because the entry is community-maintained, trust adjusts the score by -10. The entry declares no high-risk capabilities on its own, so capabilities add nothing. It matches no dangerous capability combinations. The clamped result is 40, placing it in the medium band.

See the full scoring formula →

Findings

  • Established community project Trust offset
    Contribution to score: -10

Capabilities

Every capability the entry declares, with the security implication of each.

  • browser:control Browser control
    Drives a browser session. Combined with credential access can impersonate the user on web services.
  • network:outbound Outbound network
    Can make outbound network requests. Required for hosted model providers and remote APIs; also the path for data exfiltration if combined with read access.