Click an element in the Camoufox browser.
AI agents invoke mcp_browser_use__camoufox_click to trigger actions in MCP Browser Use. 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 browser element is an interactive browser action that triggers external operations — it can submit forms, initiate purchases, confirm dialogs, navigate pages, or trigger downloads. The effects depend on the element clicked and can be wide-ranging, making this an Execute-category tool.
From the tool's definition Click an element in the Camoufox browser
Documented attack patterns abuse exactly the kind of access mcp_browser_use__camoufox_click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Browser Use, and nothing reaches the server without passing your rules. This is the rule we recommend for mcp_browser_use__camoufox_click:
{
"version": "1",
"default": "deny",
"tools": {
"mcp_browser_use__camoufox_click": {
"limits": [
{
"counter": "mcp_browser_use__camoufox_click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}mcp_browser_use__camoufox_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 an element in the Camoufox browser. It is categorised as a Execute tool in the MCP Browser Use MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Browser Use MCP server in PolicyLayer and add a rule for mcp_browser_use__camoufox_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 MCP Browser Use. Nothing to install.
mcp_browser_use__camoufox_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 mcp_browser_use__camoufox_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 mcp_browser_use__camoufox_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.
mcp_browser_use__camoufox_click is provided by the MCP Browser Use MCP server (janspoerer/mcp_browser_use). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Browser Use, 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.
9 MCP Browser Use tools catalogued and risk-classified — across an index of 43,000+ MCP servers.