mouse_click · Windows MCP Server MCP: Risk & Policy

WHAT IT DOES

What mouse_click does on Windows MCP Server

AI agents invoke mouse_click to trigger actions in Windows 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.

WHY IT NEEDS A POLICY

Why mouse_click needs a policy

Clicking the mouse can trigger arbitrary UI actions (buttons, links, menus, confirmations) depending on what is under the cursor. This is an Execute-category action because its effects are determined by runtime context and arguments.

From the tool's definition 'Click the mouse at current position or specified coordinates' — triggers UI interactions on the Windows desktop via mouse clicks

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mouse_click Rate-limited

mouse_click stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mouse_click": {
      "limits": [
        {
          "counter": "mouse_click_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Windows MCP Server, so you can run agents against it safely.

FAQ

Questions about mouse_click

What does the mouse_click tool do? +

Click the mouse at current position or specified coordinates. It is categorised as a Execute tool in the Windows MCP Server 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 Windows MCP Server 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 Windows MCP Server. 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 Windows MCP Server MCP server (romeo2badboy-rgb/windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.