hold_key
Hold a keyboard key for a duration in milliseconds, then release it.
This record as markdown: /tools/mcp-control-plane/hold-key.md
What hold_key does on Mcp Control Plane
AI agents invoke hold_key to trigger actions in Mcp Control Plane. 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 hold_key is rated High
This tool triggers a keyboard input action on the system — an external operation that sends keystrokes to whatever window/application is active. It can be misused to trigger shortcuts, enter text, or manipulate UI elements in unpredictable ways, making it Execute category. Severity is medium because the blast radius depends on context but could affect active applications or system state.
From the tool's definition Hold a keyboard key for a duration in milliseconds, then release it.
Attacks that exploit this kind of access
The rule that runs hold_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Control Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hold_key, this is the rule to start with:
hold_key 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every hold_key call is checked against it from then on.
Questions about hold_key
Hold a keyboard key for a duration in milliseconds, then release it. It is categorised as a Execute tool in the Mcp Control Plane MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for hold_key: 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 Mcp Control Plane. Nothing to install.
hold_key is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the hold_key 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 hold_key. 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.
hold_key is provided by the Mcp Control Plane MCP server (albertik322-sudo/mcp-control-plane). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Control Plane, and thousands of servers like it.
Across the catalogue