Middle-click (scroll-wheel click) at the given coordinates.
AI agents invoke middle_click to trigger actions in Computer Use MCP Server. 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.
Performs a physical mouse interaction on the desktop UI. Clicking can trigger UI actions, open links, close tabs, or invoke context-dependent behaviors depending on what is at the target coordinates. This is an execution of a desktop action with effects that depend on arguments (coordinates), making it Execute category.
From the tool's definition Middle-click (scroll-wheel click) at the given coordinates
Attacks that exploit this kind of access
Middle-click (scroll-wheel click) at the given coordinates. It is categorised as a Execute tool in the Computer Use MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Computer Use MCP Server MCP server in PolicyLayer and add a rule for middle_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 Computer Use MCP Server. Nothing to install.
middle_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 middle_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 middle_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.
middle_click is provided by the Computer Use MCP Server MCP server (syedazharmbnr1/computer-use-mcp). 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 →