key_up

Release a keyboard key.

SERVERMcp Control Plane SOURCEalbertik322-sudo/mcp-control-plane

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mcp-control-plane/key-up.md

WHAT IT DOES

What key_up does on Mcp Control Plane

AI agents invoke key_up 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.

RISK

Why key_up is rated High

Releasing a keyboard key triggers an external operation (a simulated keyboard input event) on the target system. This is an action with side effects that depends on which key is specified. While it may seem benign in isolation, it can be chained with other key actions to execute commands, bypass security prompts, or interact with active windows in unintended ways.

From the tool's definition Release a keyboard key

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs key_up 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 key_up, this is the rule to start with:

key_up Rate-limited

key_up 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": {
    "key_up": {
      "limits": [
        {
          "counter": "key_up_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Control Plane, apply this rule, and every key_up call is checked against it from then on.

FAQ

Questions about key_up

What does the key_up tool do? +

Release a keyboard key. 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.

How do I enforce a policy on key_up? +

Register the Mcp Control Plane MCP server in PolicyLayer and add a rule for key_up: 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.

What risk level is key_up? +

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

Can I rate-limit key_up? +

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

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

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

KEEP EXPLORING

More on Mcp Control Plane, and thousands of servers like it.

This server

All 286 Mcp Control Plane tools → High-risk tools on this server →

Across the catalogue

qt_key_press on Qt →send_key_to_window on Frida Game Hacking MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →