mouse_click
Click on the real desktop at screen coordinates.
This record as markdown: /tools/335234131-agent-browser-mcp/mouse-click.md
What mouse_click does on Agent Browser
AI agents invoke mouse_click to trigger actions in Agent Browser. 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.
Why mouse_click is rated High
Clicking on screen coordinates in a real browser with active sessions can trigger arbitrary UI actions — submitting forms, clicking buttons, navigating pages, or initiating transactions. The effect is entirely dependent on what is at the target coordinates, making this an Execute-class tool with high severity due to the real browser context with authenticated sessions.
From the tool's definition 'Click on the real desktop at screen coordinates' — triggers physical mouse click actions in a real browser/desktop environment with full session context including login sessions and cookies
Attacks that exploit this kind of access
The rule that runs mouse_click safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Browser, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mouse_click, this is the rule to start with:
mouse_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Agent Browser, apply this rule, and every mouse_click call is checked against it from then on.
Questions about mouse_click
Click on the real desktop at screen coordinates. It is categorised as a Execute tool in the Agent Browser MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Agent Browser MCP server in PolicyLayer and add a rule for mouse_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 Agent Browser. Nothing to install.
mouse_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 mouse_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 mouse_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.
mouse_click is provided by the Agent Browser MCP server (335234131/agent-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Agent Browser, and thousands of servers like it.
Across the catalogue