List all calendars accessible to the user.
AI agents call list_calendars to retrieve information from Google Workspace Mcp Sidecar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns calendar data without any side effects. It falls clearly into the Read category as it retrieves information only. The severity is low because listing calendars exposes metadata about calendar availability but does not access sensitive event details, modify data, or enable further actions without additional tool calls.
From the tool's definition Tool name is 'list_calendars' and description states it 'List[s] all calendars accessible to the user.' This is a retrieval operation with no modification, deletion, or execution of external commands.
Attacks that exploit this kind of access
List all calendars accessible to the user. It is categorised as a Read tool in the Google Workspace Mcp Sidecar MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace Mcp Sidecar 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 Google Workspace Mcp Sidecar. 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 Google Workspace Mcp Sidecar MCP server (milad/google-mcp-sidecar). 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 →