Click an element by snapshot ref (e.g., 's1e5' for main frame or 's1f2e10' for iframe elements). Returns: (1) shortened YAML snapshot text, (2) base64 PNG screenshot, (3) base64 PNG screenshot with refs. Note: Snapshot is shortened by default. If you see an element in the screenshot that has no r...
AI agents invoke browser_click to trigger actions in Search. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
target | string | Yes | Element target: snapshot ref such as "s1e1" for main frame or "s1f2e5" for iframe elements (coordinates are also accepted). |
Parameters from the server's own tool schema.
Clicking UI elements in a browser can trigger a wide range of actions depending on what is clicked — form submissions, purchases, deletions, navigation, downloads, etc. The actual effect is entirely argument-dependent and can span multiple severity levels. This qualifies as Execute with high severity due to the broad and unpredictable blast radius of arbitrary click actions on web pages.
From the tool's definition Click an element by snapshot ref... triggers external operations whose effects depend on arguments
Attacks that exploit this kind of access
Click an element by snapshot ref (e.g., 's1e5' for main frame or 's1f2e10' for iframe elements). Returns: (1) shortened YAML snapshot text, (2) base64 PNG screenshot, (3) base64 PNG screenshot with refs. Note: Snapshot is shortened by default. If you see an element in the screenshot that has no ref in the snapshot, call browser_snapshot with detail='all' to get the full snapshot. Warning: Snapshot may not reflect latest page state due to async web content; call browser_snapshot to get current state if needed. It is categorised as a Execute tool in the Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
browser_click accepts 1 parameter: target. Required: target. The full parameter table on this page comes from the server's own tool schema.
Register the Search MCP server in PolicyLayer and add a rule for browser_click: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Search. Nothing to install.
browser_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the browser_click rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for browser_click. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
browser_click is provided by the Search MCP server (search-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →