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

computer_right_click

Right-click at x,y (screenshot coordinates). Requires approval (risk 3).

SERVERLocalAnt SOURCEyuga-hashimoto/localant
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/yuga-hashimoto-localant/computer-right-click.md

What computer_right_click does on LocalAnt

AI agents invoke computer_right_click to trigger actions in LocalAnt. 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 computer_right_click is rated High

This tool triggers a browser/desktop UI interaction (right-click) at specified screen coordinates. It executes an action on the local PC that can open context menus, trigger context-sensitive operations, or interact with arbitrary UI elements depending on what is on screen. It falls under Execute as it drives external operations whose effects depend on the arguments (coordinates).

From the tool's definition Right-click at x,y (screenshot coordinates). Requires approval (risk 3).

Questions about computer_right_click

What does the computer_right_click tool do? +

Right-click at x,y (screenshot coordinates). Requires approval (risk 3). It is categorised as a Execute tool in the LocalAnt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on computer_right_click? +

Register the LocalAnt MCP server in PolicyLayer and add a rule for computer_right_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 LocalAnt. Nothing to install.

What risk level is computer_right_click? +

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

Can I rate-limit computer_right_click? +

Yes. Add a rate_limit block to the computer_right_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 computer_right_click completely? +

Set action: deny in the PolicyLayer policy for computer_right_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 computer_right_click? +

computer_right_click is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on LocalAnt, 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 LocalAnt'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.