cond_save_hotkeys · TermPipe MCP: Risk & Policy

WHAT IT DOES

What cond_save_hotkeys does on TermPipe MCP

AI agents use cond_save_hotkeys to create or update resources in TermPipe MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TermPipe MCP environment.

WHY IT NEEDS A POLICY

Why cond_save_hotkeys needs a policy

This tool creates or modifies a file on disk containing hotkey configuration. While the operation is reversible (the file can be edited or deleted), it persists state changes to the filesystem. In the context of a terminal access server (TermPipe MCP), saving hotkey configurations could affect system behavior or create persistence mechanisms.

From the tool's definition Tool name is 'cond_save_hotkeys' with description 'Save current hotkey config to a file.' The verb 'save' and direct reference to writing configuration to a file indicate a Write operation that modifies filesystem state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cond_save_hotkeys Rate-limited

cond_save_hotkeys stays usable, but capped — an agent stuck in a loop can't make hundreds of changes 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_save_hotkeys": {
      "limits": [
        {
          "counter": "cond_save_hotkeys_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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_save_hotkeys

What does the cond_save_hotkeys tool do? +

Save current hotkey config to a file. It is categorised as a Write tool in the TermPipe MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on cond_save_hotkeys? +

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

cond_save_hotkeys is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cond_save_hotkeys? +

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

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

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