Get user
AI agents call get_events to retrieve information from MCP Calendar Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries/retrieves calendar events without side effects. It does not create, modify, delete, or execute operations—it only returns event data to the user. This is a straightforward read operation with minimal risk if misused by an AI agent, as it only exposes calendar data visibility.
From the tool's definition Tool name 'get_events' and sibling context (add_event, delete_event, update_event) indicate a retrieval operation. Server description mentions 'checking schedules' as a read operation.
Attacks that exploit this kind of access
Get user. It is categorised as a Read tool in the MCP Calendar Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Calendar Server MCP server in PolicyLayer and add a rule for get_events: 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 MCP Calendar Server. Nothing to install.
get_events 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_events 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_events. 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_events is provided by the MCP Calendar Server MCP server (tekuor/mcp-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 →