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.
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).
Attacks that exploit this kind of access
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.
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.
computer_right_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 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.
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.
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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →