New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

mouse_click

Click on the real desktop at screen coordinates.

SERVERAgent Browser SOURCE335234131/agent-browser-mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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

Questions about mouse_click

What does the mouse_click tool do? +

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.

How do I enforce a policy on mouse_click? +

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.

What risk level is mouse_click? +

mouse_click is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit mouse_click? +

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.

How do I block mouse_click completely? +

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.

What MCP server provides mouse_click? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Agent Browser's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.