list_calendars
AI agents call list_calendars to retrieve information from Calendar App without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries calendar data with no side effects. Listing calendars is a read-only operation that does not modify, delete, or execute any actions. The blast radius of misuse is minimal—an AI agent could only discover what calendars exist, which is low-risk information exposure.
From the tool's definition Tool name 'list_calendars' combined with server description stating 'viewing, searching, and filtering calendar data' and sibling tools like 'get_events', 'get_reminders', 'search' that are all read-only operations.
Attacks that exploit this kind of access
list_calendars. It is categorised as a Read tool in the Calendar App MCP Server, which means it retrieves data without modifying state.
Register the Calendar App MCP server in PolicyLayer and add a rule for list_calendars: 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 Calendar App. Nothing to install.
list_calendars 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_calendars 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_calendars. 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_calendars is provided by the Calendar App MCP server (rygwdn/calendar-app-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 →