Get details of a specific calendar event
AI agents call get_calendar_event to retrieve information from Enhanced MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves calendar event information without creating, modifying, deleting, or executing any actions. It is a simple query operation that returns data with no side effects. The severity is low because calendar metadata leakage poses minimal security risk compared to other categories.
From the tool's definition Tool name is 'get_calendar_event' and description states 'Get details of a specific calendar event' - a pure retrieval operation with no modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Get details of a specific calendar event. It is categorised as a Read tool in the Enhanced MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced MCP Server MCP server in PolicyLayer and add a rule for get_calendar_event: 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 Enhanced MCP Server. Nothing to install.
get_calendar_event 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_event 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_event. 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_event is provided by the Enhanced MCP Server MCP server (pbulbule13/mcpwithgoogle). 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 →