AI agents invoke keyboard_key to trigger actions in Kwin. 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.
The description is empty, but based on sibling tools (keyboard_key_down, keyboard_key_up, keyboard_type) and the server context of desktop GUI automation, this tool likely simulates keyboard key presses on a live or virtual desktop. Simulating keyboard input can trigger arbitrary actions on a desktop environment, making it an Execute-level tool.
From the tool's definition Tool name 'keyboard_key' on a server that enables GUI automation via keyboard interaction tools like keyboard_key_down, keyboard_key_up, keyboard_type
Documented attack patterns abuse exactly the kind of access keyboard_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kwin, and nothing reaches the server without passing your rules. This is the rule we recommend for keyboard_key:
{
"version": "1",
"default": "deny",
"tools": {
"keyboard_key": {
"limits": [
{
"counter": "keyboard_key_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}keyboard_key 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.
keyboard_key. It is categorised as a Execute tool in the Kwin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kwin MCP server in PolicyLayer and add a rule for keyboard_key: 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 Kwin. Nothing to install.
keyboard_key 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 keyboard_key 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 keyboard_key. 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.
keyboard_key is provided by the Kwin MCP server (isac322/kwin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kwin, 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.
30 Kwin tools catalogued and risk-classified — across an index of 43,000+ MCP servers.