cond_mouse_move · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_mouse_move does on TermPipe MCP

AI agents invoke cond_mouse_move to trigger actions in TermPipe MCP. 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 cond_mouse_move needs a policy

Moving the mouse cursor is an external operation that interacts with the system's GUI environment. It can be used to manipulate UI elements and is part of a broader terminal/automation context. It is not purely destructive or financial, but it executes a real system-level action with variable effects depending on where the cursor is moved, potentially enabling further UI interactions.

From the tool's definition Move the mouse cursor — triggers an external UI/system operation (mouse movement) whose effect depends on coordinates/arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_mouse_move Rate-limited

cond_mouse_move 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": {
    "cond_mouse_move": {
      "limits": [
        {
          "counter": "cond_mouse_move_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 TermPipe MCP, so you can run agents against it safely.

FAQ

Questions about cond_mouse_move

What does the cond_mouse_move tool do? +

Move the mouse cursor. It is categorised as a Execute tool in the TermPipe MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cond_mouse_move? +

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

What risk level is cond_mouse_move? +

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

Can I rate-limit cond_mouse_move? +

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

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

cond_mouse_move is provided by the TermPipe MCP server (wbind-core/termpipe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.