cond_move_window · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_move_window does on TermPipe MCP

AI agents invoke cond_move_window 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_move_window needs a policy

This tool triggers an external UI operation (moving a window on screen), which is an action with side effects on the desktop environment. It falls under Execute as it manipulates external system state (window position) rather than reading or writing data files. Misuse could interfere with user workflows or be used to obscure/reposition windows, but the blast radius is moderate.

From the tool's definition Move a window. x/y can be pixels or 0.0-1.0 percentage of screen.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_move_window Rate-limited

cond_move_window 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_move_window": {
      "limits": [
        {
          "counter": "cond_move_window_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_move_window

What does the cond_move_window tool do? +

Move a window. x/y can be pixels or 0.0-1.0 percentage of screen. 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_move_window? +

Register the TermPipe MCP server in PolicyLayer and add a rule for cond_move_window: 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_move_window? +

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

Can I rate-limit cond_move_window? +

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

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

cond_move_window 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.