cond_register_hotkey_script · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_register_hotkey_script does on TermPipe MCP

AI agents invoke cond_register_hotkey_script 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_script needs a policy

This tool binds a hotkey to a shell script, enabling arbitrary shell script execution. When triggered, it runs shell commands on the system. The Execute category applies because it triggers external operations (shell scripts) whose effects depend on arguments.

From the tool's definition Register a hotkey to execute a shell script

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_register_hotkey_script Rate-limited

cond_register_hotkey_script 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_script": {
      "limits": [
        {
          "counter": "cond_register_hotkey_script_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_script

What does the cond_register_hotkey_script tool do? +

Register a hotkey to execute a shell script. 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_script? +

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

cond_register_hotkey_script 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_script? +

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

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

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