Check if a proposed time slot conflicts with existing events. Returns conflicting events and suggests alternative times.
AI agents call check_conflicts 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.
check_conflicts performs conflict detection by querying existing events and comparing them against a proposed time slot. It returns information (conflicting events, suggestions) without creating, modifying, deleting, or executing any operations. This is purely informational/analytical with no side effects, placing it squarely in the Read category with low severity.
From the tool's definition Tool description states it 'Check[s] if a proposed time slot conflicts with existing events' and 'Returns conflicting events and suggests alternative times.' These are read-only query operations that retrieve and analyze existing calendar data without…
Attacks that exploit this kind of access
Check if a proposed time slot conflicts with existing events. Returns conflicting events and suggests alternative times. 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 check_conflicts: 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.
check_conflicts 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 check_conflicts 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 check_conflicts. 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.
check_conflicts 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 →