AI agents invoke send_keyboard_shortcut to trigger actions in MCP Windows. 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.
Sending keyboard shortcuts executes actions on the operating system or active applications (e.g., Ctrl+C, Alt+F4, Win+R). This can trigger arbitrary system operations depending on the shortcut sent, making it an Execute-category tool with high severity since it could be misused to launch programs, close windows, or invoke system commands. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'send_keyboard_shortcut' implies triggering keyboard input/actions on the system; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access send_keyboard_shortcut gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Windows, and nothing reaches the server without passing your rules. This is the rule we recommend for send_keyboard_shortcut:
{
"version": "1",
"default": "deny",
"tools": {
"send_keyboard_shortcut": {
"limits": [
{
"counter": "send_keyboard_shortcut_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_keyboard_shortcut 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.
Free to start. No card required.
send_keyboard_shortcut. It is categorised as a Execute tool in the MCP Windows MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Windows MCP server in PolicyLayer and add a rule for send_keyboard_shortcut: 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 Windows. Nothing to install.
send_keyboard_shortcut is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_keyboard_shortcut 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.
Set action: deny in the PolicyLayer policy for send_keyboard_shortcut. 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.
send_keyboard_shortcut is provided by the MCP Windows MCP server (secretiveshell/mcp-windows). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Windows, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
28 MCP Windows tools catalogued and risk-classified — across an index of 43,000+ MCP servers.