Find matching events between two calendars or providers. Useful for identifying duplicates or corresponding events across different calendar systems.
AI agents call find_matching_events 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 compares event data across calendar systems to detect matches. It has no side effects on calendar state—it neither creates, modifies, nor deletes events. The blast radius of misuse is minimal: an agent could query sensitive event information, but cannot alter calendars or cause irreversible changes. This is a straightforward Read classification.
From the tool's definition Tool description states it finds and identifies matching events between calendars—a retrieval and comparison operation with no modification capability.
Attacks that exploit this kind of access
Find matching events between two calendars or providers. Useful for identifying duplicates or corresponding events across different calendar systems. 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 find_matching_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 Calendar MCP Server. Nothing to install.
find_matching_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 find_matching_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 find_matching_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.
find_matching_events 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 →