Find available time slots in the calendar for a given activity.
AI agents call find_free_slot to retrieve information from Calendar Pa without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads/queries calendar data to identify free slots. It does not create, modify, delete, or execute external operations. It is purely informational, similar to a calendar search or filter. Even in the context of a scheduling system with sibling tools like create_event and delete_event, this specific tool performs only a Read operation.
From the tool's definition Tool name and description indicate it 'Find[s] available time slots in the calendar' — a query operation that retrieves calendar data without modifying it. No side effects mentioned.
Attacks that exploit this kind of access
Find available time slots in the calendar for a given activity. It is categorised as a Read tool in the Calendar Pa MCP Server, which means it retrieves data without modifying state.
Register the Calendar Pa MCP server in PolicyLayer and add a rule for find_free_slot: 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 Pa. Nothing to install.
find_free_slot 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_free_slot 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_free_slot. 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_free_slot is provided by the Calendar Pa MCP server (richardilemon/calendar-pa). 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 →