AI agents call export_calendar_ics to retrieve information from Todos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and exports calendar data as ICS text. It retrieves existing calendar events without modifying, deleting, or executing anything. The word 'export' and 'deterministic ICS text' indicate a pure read operation with no side effects.
From the tool's definition Export local calendar events as deterministic ICS text
Attacks that exploit this kind of access
Export local calendar events as deterministic ICS text. It is categorised as a Read tool in the Todos MCP Server, which means it retrieves data without modifying state.
Register the Todos MCP server in PolicyLayer and add a rule for export_calendar_ics: 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 Todos. Nothing to install.
export_calendar_ics 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 export_calendar_ics 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 export_calendar_ics. 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.
export_calendar_ics is provided by the Todos MCP server (@hasna/todos). 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 →