Release the left mouse button at the current cursor position. ${FRONTMOST_GATE_DESC}
AI agents invoke left_mouse_up to trigger actions in Computer Use Windows. 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.
Releasing the mouse button is a UI interaction primitive that completes drag-and-drop or click operations. It triggers external operations whose effects depend on context (e.g., completing a drag, releasing a held click), placing it in Execute. Severity is medium because misuse could trigger unintended UI actions, but the impact is bounded by what's on screen.
From the tool's definition Release the left mouse button at the current cursor position
Attacks that exploit this kind of access
Release the left mouse button at the current cursor position. ${FRONTMOST_GATE_DESC}. It is categorised as a Execute tool in the Computer Use Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Computer Use Windows MCP server in PolicyLayer and add a rule for left_mouse_up: 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 Windows. Nothing to install.
left_mouse_up 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 left_mouse_up 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 left_mouse_up. 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.
left_mouse_up is provided by the Computer Use Windows MCP server (wimi321/windows-computer-use-skill). 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 →