hotkey
AI agents invoke hotkey to trigger actions in macOS Control MCP Server. 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.
A hotkey tool on a desktop automation server triggers keyboard shortcuts that can execute arbitrary system-level actions (e.g., Cmd+Q to quit apps, Cmd+Space to open Spotlight, etc.). The description is empty, but context from sibling tools (key_down, key_up) and the server description confirm this executes keyboard input. This falls under Execute as it triggers external operations whose effects depend on arguments.
From the tool's definition Tool name 'hotkey' on a macOS desktop automation server that 'Enables full desktop automation on macOS through natural language, including mouse control, keyboard input, screen capture, and GUI interaction using PyAutoGUI'.
Attacks that exploit this kind of access
hotkey. It is categorised as a Execute tool in the macOS Control MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the macOS Control MCP Server MCP server in PolicyLayer and add a rule for hotkey: 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 macOS Control MCP Server. Nothing to install.
hotkey 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 hotkey 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 hotkey. 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.
hotkey is provided by the macOS Control MCP Server MCP server (lodimup/macos-control-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 →