Return posts that match user-provided interests such as Siri, Xcode, hardware, release dates, or Apple Intelligence.
AI agents call get_noteworthy_updates to retrieve information from Apple Event without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries a liveblog database for posts matching filter criteria (Siri, Xcode, hardware, etc.). It retrieves and presents data only; it does not modify, delete, execute code, or perform financial operations. The blast radius of misuse is minimal—an agent could retrieve unwanted posts but cannot harm systems or data integrity.
From the tool's definition Tool returns/retrieves posts matching user interests ("Return posts"). No modification, deletion, or execution described.
Attacks that exploit this kind of access
Return posts that match user-provided interests such as Siri, Xcode, hardware, release dates, or Apple Intelligence. It is categorised as a Read tool in the Apple Event MCP Server, which means it retrieves data without modifying state.
Register the Apple Event MCP server in PolicyLayer and add a rule for get_noteworthy_updates: 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 Event. Nothing to install.
get_noteworthy_updates is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_noteworthy_updates 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 get_noteworthy_updates. 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.
get_noteworthy_updates is provided by the Apple Event MCP server (perryraskin/apple-event-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 →