Send a notification on macOS using osascript
AI agents invoke send_notification to trigger actions in Apple Notifier. 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 uses osascript, a system-level script execution engine, to send notifications. While the primary effect is displaying a notification, osascript is a general execution environment that could have broader system effects. Misuse could result in spam notifications or, depending on implementation, more significant actions via AppleScript.
From the tool's definition 'Send a notification on macOS using osascript' — osascript executes AppleScript/JXA code on the system
Attacks that exploit this kind of access
Send a notification on macOS using osascript. It is categorised as a Execute tool in the Apple Notifier MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Apple Notifier MCP server in PolicyLayer and add a rule for send_notification: 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 Apple Notifier. Nothing to install.
send_notification 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 send_notification 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 send_notification. 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.
send_notification is provided by the Apple Notifier MCP server (piatra-automation/apple-notifier-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 →