Run an AppleScript command. For controlling Finder, Safari, Mail, Notes, etc. (macOS only). WARNING: Executes arbitrary AppleScript — can perform destructive actions (delete files, send emails). All executions are audit-logged.
AI agents invoke applescript to trigger actions in ScreenHand. 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, which can perform a wide range of actions including destructive ones (deleting files) and high-impact ones (sending emails). While it spans Execute, Destructive, and even potentially Financial categories, the primary classification is Execute because the actual effect depends entirely on the script passed as an argument.
From the tool's definition 'Run an AppleScript command' and 'WARNING: Executes arbitrary AppleScript — can perform destructive actions (delete files, send emails)'
Documented attack patterns abuse exactly the kind of access applescript gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ScreenHand, and nothing reaches the server without passing your rules. This is the rule we recommend for applescript:
{
"version": "1",
"default": "deny",
"tools": {
"applescript": {
"limits": [
{
"counter": "applescript_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}applescript 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.
Run an AppleScript command. For controlling Finder, Safari, Mail, Notes, etc. (macOS only). WARNING: Executes arbitrary AppleScript — can perform destructive actions (delete files, send emails). All executions are audit-logged. It is categorised as a Execute tool in the ScreenHand MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ScreenHand MCP server in PolicyLayer and add a rule for 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 ScreenHand. Nothing to install.
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 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 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.
applescript is provided by the ScreenHand MCP server (manushi4/screenhand). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ScreenHand, 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.
89 ScreenHand tools catalogued and risk-classified — across an index of 43,000+ MCP servers.