AI agents invoke puppeteer_click to trigger actions in MCP-Brave-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.
Clicking UI elements can trigger arbitrary side effects: form submissions, deletions, navigation, purchases, etc. This is a browser automation action whose consequences are entirely argument-dependent, making it Execute with high severity due to potential for misuse.
From the tool's definition 'Click an element on the page' — triggers a browser action (puppeteer click) whose effects depend on what element is clicked
Documented attack patterns abuse exactly the kind of access puppeteer_click gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Brave-Search, and nothing reaches the server without passing your rules. This is the rule we recommend for puppeteer_click:
{
"version": "1",
"default": "deny",
"tools": {
"puppeteer_click": {
"limits": [
{
"counter": "puppeteer_click_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}puppeteer_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 on the page. It is categorised as a Execute tool in the MCP-Brave-Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP-Brave-Search MCP server in PolicyLayer and add a rule for puppeteer_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-Brave-Search. Nothing to install.
puppeteer_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 puppeteer_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 puppeteer_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.
puppeteer_click is provided by the MCP-Brave-Search MCP server (modelcontextprotocol/servers-archived). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Brave-Search, 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.
59 MCP-Brave-Search tools catalogued and risk-classified — across an index of 43,000+ MCP servers.