Fetch raw ICS for ids returned by search().
AI agents call fetch to retrieve information from iCloud CalDAV MCP Connector without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation only—it fetches calendar data in ICS format without creating, modifying, or deleting any information. It is a read-only query operation with no side effects. While the server overall includes destructive tools (delete_event) and write operations (create_event, update_event), this specific tool is limited to data retrieval, placing it in the Read category with low severity.
From the tool's definition Tool name is 'fetch' and description states it retrieves 'raw ICS' data returned by prior search results. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
Fetch raw ICS for ids returned by search(). It is categorised as a Read tool in the iCloud CalDAV MCP Connector MCP Server, which means it retrieves data without modifying state.
Register the iCloud CalDAV MCP Connector MCP server in PolicyLayer and add a rule for fetch: 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 iCloud CalDAV MCP Connector. Nothing to install.
fetch 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 fetch 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 fetch. 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.
fetch is provided by the iCloud CalDAV MCP Connector MCP server (localhost433/icloud-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 →