click_mouse · Macinput MCP: Risk & Policy

WHAT IT DOES

What click_mouse does on Macinput

AI agents invoke click_mouse to trigger actions in Macinput. 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 click_mouse needs a policy

Mouse clicking triggers UI interactions on the desktop — buttons, links, menus, confirmations — whose effects depend entirely on what is under the cursor at execution time. This can chain into any downstream action (file deletion, form submission, purchases, etc.), making it an Execute-category tool with high severity due to the broad blast radius of unintended clicks in a desktop GUI automation context.

From the tool's definition Click at the current cursor location or at explicit coordinates

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

click_mouse Rate-limited

click_mouse 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": {
    "click_mouse": {
      "limits": [
        {
          "counter": "click_mouse_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 Macinput, so you can run agents against it safely.

FAQ

Questions about click_mouse

What does the click_mouse tool do? +

Click at the current cursor location or at explicit coordinates. It is categorised as a Execute tool in the Macinput MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on click_mouse? +

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

What risk level is click_mouse? +

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

Can I rate-limit click_mouse? +

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

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

click_mouse is provided by the Macinput MCP server (sigma711/macinput). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.