Press individual keyboard keys. Supports special keys like
AI agents invoke Key-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.
Pressing keys can trigger arbitrary system actions (e.g., Enter to confirm dialogs, Delete to remove files, Win+R to run commands). Combined with sibling tools like Powershell-Tool and Launch-Tool on a Windows automation server, keystroke injection represents an Execute-level capability with high blast radius. The description is sparse, lowering confidence slightly, but the tool's nature is clear from context.
From the tool's definition 'Press individual keyboard keys. Supports special keys' — simulates keyboard input on the Windows OS, triggering system-level actions depending on which keys are pressed
Attacks that exploit this kind of access
Press individual keyboard keys. Supports special keys like. 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.
Register the Windows- MCP server in PolicyLayer and add a rule for Key-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.
Key-Tool 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 Key-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.
Set action: deny in the PolicyLayer policy for Key-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.
Key-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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →