Clear all registered hotkeys.
AI agents call cond_clear_hotkeys to permanently remove resources in TermPipe MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing all registered hotkeys is a destructive operation that removes configuration data with no indication of reversibility. While hotkeys can theoretically be re-registered, the act of clearing them all at once is a bulk deletion that could disrupt workflows and automation.
From the tool's definition 'Clear all registered hotkeys' — removes/deletes all registered hotkey configurations irreversibly
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Clear all registered hotkeys. It is categorised as a Destructive tool in the TermPipe MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TermPipe MCP server in PolicyLayer and add a rule for cond_clear_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.
cond_clear_hotkeys is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cond_clear_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.
Set action: deny in the PolicyLayer policy for cond_clear_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.
cond_clear_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →