gcal_list_calendars
AI agents call gcal_list_calendars to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool lists calendars, which is a read-only query operation that retrieves existing data without side effects. The empty description reduces confidence slightly, but the naming convention and server context (which exposes 390 tools across many SaaS providers) strongly indicate this is a standard API read operation.
From the tool's definition Tool name 'gcal_list_calendars' indicates a list operation that retrieves calendar information; the 'list' verb combined with sibling patterns (e.g., airtable_list_records, amplitude_get_event_counts) confirms this is a data retrieval action with no…
Attacks that exploit this kind of access
gcal_list_calendars. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for gcal_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 Integrations MCP. Nothing to install.
gcal_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 gcal_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 gcal_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.
gcal_list_calendars is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →