calendar_weekly_summary
AI agents call calendar_weekly_summary 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.
Although the description is empty, the tool name and context from sibling read-only operations strongly suggest this retrieves and summarizes calendar data without side effects. No destructive, write, execute, or financial operations are implied. Classification as Read is appropriate with moderately high confidence despite the missing description.
From the tool's definition Tool name 'calendar_weekly_summary' implies retrieval of calendar data for a summary view. The server description indicates it 'manage[s] events, search[es] agendas, and check[s] availability', and sibling tools include 'calendar_daily_agenda',…
Attacks that exploit this kind of access
calendar_weekly_summary. 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 calendar_weekly_summary: 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.
calendar_weekly_summary 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_weekly_summary 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_weekly_summary. 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_weekly_summary is provided by the Google Calendar MCP Server MCP server (murphy360/mcp_google_calendar). 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 →