Get all Google Calendars accessible to the user
AI agents call get_all_calendars to retrieve information from Google 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 a list of calendars without altering, deleting, or executing any operations. It is a read-only query operation with minimal blast radius—an AI agent listing calendars poses negligible security risk compared to creating, modifying, or canceling events.
From the tool's definition Tool name 'get_all_calendars' and description 'Get all Google Calendars accessible to the user' indicate data retrieval with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get all Google Calendars accessible to the user. It is categorised as a Read tool in the Google Calendar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Google Calendar MCP Server MCP server in PolicyLayer and add a rule for get_all_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 Google Calendar MCP Server. Nothing to install.
get_all_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_all_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_all_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_all_calendars is provided by the Google Calendar MCP Server MCP server (shameerpc5029/google-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 →