cond_register_hotkey_input · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_register_hotkey_input does on TermPipe MCP

AI agents invoke cond_register_hotkey_input 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_register_hotkey_input needs a policy

This tool registers hotkeys that trigger input commands including typing, key presses, and mouse clicks. These are UI automation/execution actions that can interact with any application on the system, potentially performing arbitrary actions depending on what commands are bound.

From the tool's definition Register a hotkey to execute input commands (type, key, click, etc)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_register_hotkey_input Rate-limited

cond_register_hotkey_input 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_register_hotkey_input": {
      "limits": [
        {
          "counter": "cond_register_hotkey_input_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_register_hotkey_input

What does the cond_register_hotkey_input tool do? +

Register a hotkey to execute input commands (type, key, click, etc). 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_register_hotkey_input? +

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

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

Can I rate-limit cond_register_hotkey_input? +

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

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

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