Shortcut-Tool · Windows- MCP: Risk & Policy

WHAT IT DOES

What Shortcut-Tool does on Windows-MCP

AI agents invoke Shortcut-Tool to trigger actions in Windows-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 Shortcut-Tool needs a policy

Keyboard shortcuts can trigger application actions, system dialogs, file operations, and workflows whose effects depend entirely on what application is in focus and what shortcuts are configured. This makes it an Execute-category tool rather than a simple Read or Write operation. While not inherently Destructive, a shortcut like Ctrl+Shift+Delete or application-specific destructive commands could cause data loss.

From the tool's definition Tool description states 'Execute keyboard shortcuts using key combinations.' The verb 'Execute' combined with the ability to trigger arbitrary keyboard shortcuts on a Windows system creates significant potential for unintended side effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

Shortcut-Tool Rate-limited

Shortcut-Tool 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": {
    "Shortcut-Tool": {
      "limits": [
        {
          "counter": "shortcut-tool_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 Windows-MCP, so you can run agents against it safely.

FAQ

Questions about Shortcut-Tool

What does the Shortcut-Tool tool do? +

Execute keyboard shortcuts using key combinations. Pass keys as list (e.g., [. It is categorised as a Execute tool in the Windows-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 Shortcut-Tool? +

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

What risk level is Shortcut-Tool? +

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

Can I rate-limit Shortcut-Tool? +

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

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

Shortcut-Tool is provided by the Windows- MCP server (zhouke2020/cursortouch-windows-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.