event_subscribe
Start real-time monitoring of Apple data changes: calendar, reminders, clipboard, mail unread count, focus mode, now-playing track, and watched file paths.
This record as markdown: /tools/heznpc-airmcp/event-subscribe.md
What event_subscribe does on AirMCP
AI agents invoke event_subscribe to trigger actions in AirMCP. 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.
Why event_subscribe is rated High
This tool executes a monitoring/subscription operation that activates real-time listeners across multiple Apple system channels (clipboard access, mail monitoring, focus mode tracking). While it does not destructively modify data or move money, it triggers ongoing external system operations whose effects persist until unsubscribed.
From the tool's definition Tool description states 'Start real-time monitoring of Apple data changes' including 'clipboard, mail unread count, focus mode, now-playing track, and watched file paths.' The use of 'real-time monitoring' and ability to subscribe to system events indicates…
Attacks that exploit this kind of access
The rule that runs event_subscribe safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AirMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For event_subscribe, this is the rule to start with:
event_subscribe 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.
The button opens the PolicyLayer dashboard: create your workspace, connect AirMCP, apply this rule, and every event_subscribe call is checked against it from then on.
Questions about event_subscribe
Start real-time monitoring of Apple data changes: calendar, reminders, clipboard, mail unread count, focus mode, now-playing track, and watched file paths. It is categorised as a Execute tool in the AirMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Air MCP server in PolicyLayer and add a rule for event_subscribe: 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 AirMCP. Nothing to install.
event_subscribe 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 event_subscribe 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 event_subscribe. 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.
event_subscribe is provided by the Air MCP server (airmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Air, and thousands of servers like it.
This server
Across the catalogue