List all available calendars for the user
AI agents call get_calendars to retrieve information from MCP Calendar Assistant without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool merely retrieves and displays a list of calendars belonging to the user. It does not create, modify, delete, or execute any operations. The only potential concern is minor privacy leakage (which calendars exist), but this is minimal information already known to the authenticated user. The blast radius of misuse is very low—an agent cannot harm anything by listing calendars.
From the tool's definition Tool name 'get_calendars' and description 'List all available calendars for the user' indicate a query/retrieval operation with no side effects. The verb 'list' is a classic Read operation.
Attacks that exploit this kind of access
List all available calendars for the user. It is categorised as a Read tool in the MCP Calendar Assistant MCP Server, which means it retrieves data without modifying state.
Register the MCP Calendar Assistant MCP server in PolicyLayer and add a rule for get_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 MCP Calendar Assistant. Nothing to install.
get_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 get_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 get_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.
get_calendars is provided by the MCP Calendar Assistant MCP server (momer17/mailmcp). 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 →