press_hotkey · Simple MCP: Risk & Policy

WHAT IT DOES

What press_hotkey does on Simple MCP

AI agents invoke press_hotkey to trigger actions in Simple 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 press_hotkey needs a policy

Pressing hotkeys triggers external system operations whose effects depend on the key combination used. An AI agent could misuse this to trigger arbitrary system shortcuts (e.g., Alt+F4, Ctrl+Alt+Del, Win+R to open Run dialog), potentially causing unintended application closures, system actions, or launching processes, making it an Execute-category tool with high severity.

From the tool's definition Press a combination of keys as a hotkey (e.g., ctrl, tab)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

press_hotkey Rate-limited

press_hotkey 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": {
    "press_hotkey": {
      "limits": [
        {
          "counter": "press_hotkey_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 Simple MCP, so you can run agents against it safely.

FAQ

Questions about press_hotkey

What does the press_hotkey tool do? +

Press a combination of keys as a hotkey (e.g., ctrl, tab). It is categorised as a Execute tool in the Simple 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 press_hotkey? +

Register the Simple MCP server in PolicyLayer and add a rule for press_hotkey: 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 Simple MCP. Nothing to install.

What risk level is press_hotkey? +

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

Can I rate-limit press_hotkey? +

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

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

press_hotkey is provided by the Simple MCP server (karar-hayder/simple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.