AI agents invoke open_spotlight to trigger actions in MacWright. 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.
This tool performs automated UI actions (keyboard shortcuts, typing, pressing Enter) that launch applications or open files on the host system. The effects depend entirely on the query argument — an agent could open any app or file. This constitutes executing external operations, with high severity since it can launch arbitrary applications or open arbitrary files on the macOS desktop.
From the tool's definition Presses Cmd+Space, types the query, waits for results, then presses Enter — triggers external operations by launching apps or opening files via Spotlight
Attacks that exploit this kind of access
Open an app, file, or anything via Spotlight search. Presses Cmd+Space, types the query, waits for results, then presses Enter. It is categorised as a Execute tool in the MacWright MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MacWright MCP server in PolicyLayer and add a rule for open_spotlight: 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 MacWright. Nothing to install.
open_spotlight 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 open_spotlight 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 open_spotlight. 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.
open_spotlight is provided by the MacWright MCP server (ruchit-p/macwright). 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 →