List events in a calendar within a date range. Can use common periods like
AI agents call list_events to retrieve information from Apple Calendar MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar event data within a specified date range without creating, modifying, deleting, or executing any changes. It is a pure read operation that has no side effects on the calendar state. The low severity reflects minimal blast radius if misused by an agent—only information exposure.
From the tool's definition Tool name 'list_events' and description 'List events in a calendar within a date range' indicate querying/retrieval operation with no modification of data.
Attacks that exploit this kind of access
List events in a calendar within a date range. Can use common periods like. It is categorised as a Read tool in the Apple Calendar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Apple Calendar MCP Server MCP server in PolicyLayer and add a rule for list_events: 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 Calendar MCP Server. Nothing to install.
list_events 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_events 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_events. 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_events is provided by the Apple Calendar MCP Server MCP server (null-phnix/apple-calendar-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 →