AI agents invoke browser_click to trigger actions in Concurrent Browser MCP. 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.
Clicking a page element is an active browser action whose effects are highly context-dependent. It can trigger form submissions, purchases, deletions, logins, file downloads, or other irreversible operations. Because the blast radius depends on what is clicked, and an AI agent could click destructive or financial UI elements, this is classified as Execute with high severity.
From the tool's definition "Click on a page element" — triggers a browser interaction that can submit forms, navigate pages, activate UI controls, or initiate external operations depending on the target element.
Documented attack patterns abuse exactly the kind of access browser_click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Concurrent Browser MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_click:
{
"version": "1",
"default": "deny",
"tools": {
"browser_click": {
"limits": [
{
"counter": "browser_click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_click stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Click on a page element. It is categorised as a Execute tool in the Concurrent Browser MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Concurrent Browser 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 Concurrent Browser MCP. 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 Concurrent Browser MCP server (sailaoda/concurrent-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Concurrent Browser MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Concurrent Browser MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.