Get detailed information about a specific event by ID. Returns full event details including attendees, recurrence, and online meeting links.
AI agents call get_event to retrieve information from 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 retrieves and returns event details (attendees, recurrence, meeting links) without creating, modifying, deleting, or executing any actions. It is a straightforward read operation that queries calendar data. The low severity reflects minimal blast radius—unauthorized read access to calendar events is a privacy concern but lacks the destructive, financial, or code-execution implications of higher-risk tools.
From the tool's definition Tool name 'get_event' and description 'Get detailed information about a specific event by ID. Returns full event details' explicitly indicates retrieval of data with no modification or side effects.
Attacks that exploit this kind of access
Get detailed information about a specific event by ID. Returns full event details including attendees, recurrence, and online meeting links. It is categorised as a Read tool in the Calendar MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Calendar MCP Server MCP server in PolicyLayer and add a rule for get_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 Calendar MCP Server. Nothing to install.
get_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_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_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_event is provided by the Calendar MCP Server MCP server (rauf543/calendar-mcp). 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 →