Check for scheduling conflicts in a time range across one or more accounts
AI agents call check_conflicts to retrieve information from Mail Cal Drive without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries calendar data to identify conflicts. It has no side effects, does not modify any data, and does not execute external code or operations. The severity is low because even if misused, it can only expose calendar information that the account already has access to, with no capability for destructive or financial harm.
From the tool's definition The tool performs a query operation to 'check for scheduling conflicts in a time range' across calendar accounts. It retrieves and analyzes existing calendar data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Check for scheduling conflicts in a time range across one or more accounts. It is categorised as a Read tool in the Mail Cal Drive MCP Server, which means it retrieves data without modifying state.
Register the Mail Cal Drive 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 Mail Cal Drive. 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 Mail Cal Drive MCP server (rumbitopi/mail-cal-drive-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 →