screen_hotkey · Screen Agent MCP: Risk & Policy

WHAT IT DOES

What screen_hotkey does on Screen Agent

AI agents invoke screen_hotkey to trigger actions in Screen Agent. 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 screen_hotkey needs a policy

This tool simulates hotkey presses (e.g., Ctrl+C, Ctrl+V, Enter) on a Windows desktop. Hotkeys can trigger a wide range of system and application actions depending on context — including saving files, sending messages, deleting content, executing commands, or invoking system functions.

From the tool's definition 按下快捷键组合，如Ctrl+C复制、Ctrl+V粘贴、Enter发送等 — triggers keyboard shortcut combinations on the desktop

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

screen_hotkey Rate-limited

screen_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": {
    "screen_hotkey": {
      "limits": [
        {
          "counter": "screen_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 Screen Agent, so you can run agents against it safely.

FAQ

Questions about screen_hotkey

What does the screen_hotkey tool do? +

按下快捷键组合，如Ctrl+C复制、Ctrl+V粘贴、Enter发送等。. It is categorised as a Execute tool in the Screen Agent MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on screen_hotkey? +

Register the Screen Agent MCP server in PolicyLayer and add a rule for screen_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 Screen Agent. Nothing to install.

What risk level is screen_hotkey? +

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

Can I rate-limit screen_hotkey? +

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

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

screen_hotkey is provided by the Screen Agent MCP server (lqszhsp/screen-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.