List available liveblog sources, their URLs, and image support.
AI agents call list_liveblog_sources 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 retrieves metadata about available liveblog sources. It performs a simple enumeration or lookup operation that returns informational data without modifying, executing, or deleting anything. There is no capacity for financial impact, destructive action, or arbitrary code execution. The blast radius of misuse is negligible—an AI agent cannot cause harm by listing sources.
From the tool's definition Tool name 'list_liveblog_sources' and description 'List available liveblog sources, their URLs, and image support' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List available liveblog sources, their URLs, and image support. 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 list_liveblog_sources: 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.
list_liveblog_sources 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 list_liveblog_sources 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 list_liveblog_sources. 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.
list_liveblog_sources 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 →