desktop_keyboard_hotkey · MCP Desktop Tools MCP

WHAT IT DOES

What desktop_keyboard_hotkey does on MCP Desktop Tools

AI agents invoke desktop_keyboard_hotkey to trigger actions in MCP Desktop Tools. 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 desktop_keyboard_hotkey needs a policy

Pressing keyboard shortcuts can trigger arbitrary system-level actions depending on the hotkey used. Hotkeys like ctrl+alt+del, alt+f4, win+r (Run dialog), or application-specific shortcuts can close programs, open system dialogs, execute commands, or cause destructive operations.

From the tool's definition Press a keyboard shortcut (e.g. ctrl+c, alt+tab)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

desktop_keyboard_hotkey Rate-limited

desktop_keyboard_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": {
    "desktop_keyboard_hotkey": {
      "limits": [
        {
          "counter": "desktop_keyboard_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 MCP Desktop Tools, so you can run agents against it safely.

FAQ

Questions about desktop_keyboard_hotkey

What does the desktop_keyboard_hotkey tool do? +

Press a keyboard shortcut (e.g. ctrl+c, alt+tab). It is categorised as a Execute tool in the MCP Desktop Tools MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on desktop_keyboard_hotkey? +

Register the MCP Desktop Tools MCP server in PolicyLayer and add a rule for desktop_keyboard_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 MCP Desktop Tools. Nothing to install.

What risk level is desktop_keyboard_hotkey? +

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

Can I rate-limit desktop_keyboard_hotkey? +

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

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

desktop_keyboard_hotkey is provided by the MCP Desktop Tools MCP server (k1ta141k/mcp-desktop-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.