AI agents invoke browser_mouse_down to trigger actions in Playwright. 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.
Playwright is a browser automation framework. 'browser_mouse_down' almost certainly simulates a mouse button press event in the browser, which is an execution of a browser action. Sibling tools confirm this is a browser-control MCP server. Mouse actions can trigger arbitrary web application behavior depending on what is clicked.
From the tool's definition Tool name 'browser_mouse_down' on a Playwright server alongside sibling tools like browser_click, browser_drag — implies triggering a mouse button press in a browser context.
Documented attack patterns abuse exactly the kind of access browser_mouse_down gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Playwright, and nothing reaches the server without passing your rules. This is the rule we recommend for browser_mouse_down:
{
"version": "1",
"default": "deny",
"tools": {
"browser_mouse_down": {
"limits": [
{
"counter": "browser_mouse_down_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}browser_mouse_down 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.
browser_mouse_down. It is categorised as a Execute tool in the Playwright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Playwright MCP server in PolicyLayer and add a rule for browser_mouse_down: 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 Playwright. Nothing to install.
browser_mouse_down 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_mouse_down 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_mouse_down. 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_mouse_down is provided by the Playwright MCP server (@playwright/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Playwright, 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.
68 Playwright tools catalogued and risk-classified — across an index of 43,000+ MCP servers.