AI agents invoke run_applescript 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 executes arbitrary AppleScript code on the user's macOS system. AppleScript can automate any macOS application, access system features, modify files, change settings, and perform other irreversible actions depending on the script provided.
From the tool's definition Tool name is 'run_applescript' and description states 'Execute an AppleScript script' with explicit mention of 'automating macOS apps and system features'. AppleScript is a scripting language that can invoke arbitrary macOS operations.
Attacks that exploit this kind of access
Execute an AppleScript script and return the result. Supports multi-line scripts. Powerful for automating macOS apps and system features not covered by other tools. Use. 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 run_applescript: 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.
run_applescript 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 run_applescript 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 run_applescript. 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.
run_applescript 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 →