List all calendars the account can access.
AI agents call calendar_list to retrieve information from Google Workspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries calendar metadata without side effects. It performs a read-only operation analogous to 'list' or 'fetch' operations. The potential blast radius is low since the account's calendar access is already known to the authenticated user, and enumeration of calendars poses minimal risk. No data is created, modified, deleted, or executed.
From the tool's definition Tool name 'calendar_list' and description 'List all calendars the account can access' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
List all calendars the account can access. It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP server in PolicyLayer and add a rule for calendar_list: 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 Workspace. Nothing to install.
calendar_list 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 calendar_list 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 calendar_list. 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.
calendar_list is provided by the Google Workspace MCP server (rajool/google-workspace-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 →