Returns metadata for a calendar
AI agents call get_calendar 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 queries calendar metadata without creating, modifying, deleting, or executing operations. It is a straightforward read operation that retrieves information about a calendar. Low severity because exposure of calendar metadata alone has limited blast radius—metadata typically contains non-sensitive structural information unless the calendar system exposes sensitive details through metadata fields.
From the tool's definition Tool name 'get_calendar' combined with description 'Returns metadata for a calendar' indicates a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Returns metadata for a calendar. 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_calendar: 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_calendar 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_calendar 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_calendar. 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_calendar is provided by the Google Calendar MCP Server MCP server (sohamkapileshwar2/google-calendar-mcp-server). 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 →