AI agents invoke keyboard_shortcut to trigger actions in MaaMCP. 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.
Given the server's purpose of Android and Windows desktop automation, a 'keyboard_shortcut' tool almost certainly triggers keyboard shortcut actions on the controlled device (e.g., Ctrl+C, Alt+F4, Win+D). This constitutes executing an external operation on a device. The empty description lowers confidence, but sibling tools like 'click', 'click_key', and 'double_click' confirm this is an automation/execution server.
From the tool's definition Tool name 'keyboard_shortcut' on a server providing Android/Windows desktop automation capabilities; description is empty and uninformative.
Attacks that exploit this kind of access
keyboard_shortcut. It is categorised as a Execute tool in the MaaMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Maa MCP server in PolicyLayer and add a rule for 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 MaaMCP. Nothing to install.
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 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 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.
keyboard_shortcut is provided by the Maa MCP server (maa-ai/maamcp). 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 →