Get available time slots for an event type
AI agents call check_availability to retrieve information from Mcp Calendly without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves calendar availability data without creating, modifying, deleting, or executing any actions. It has no side effects on calendar state and minimal blast radius if an AI agent misuses it—the worst outcome would be reading someone's availability information, which is typically intended to be shared for scheduling purposes.
From the tool's definition Tool description states 'Get available time slots' which is a retrieval operation with no side effects. Sibling tools confirm this is a Calendly integration; checking availability is fundamentally a read-only query.
Attacks that exploit this kind of access
Get available time slots for an event type. It is categorised as a Read tool in the Mcp Calendly MCP Server, which means it retrieves data without modifying state.
Register the Mcp Calendly MCP server in PolicyLayer and add a rule for check_availability: 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 Mcp Calendly. Nothing to install.
check_availability 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_availability 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_availability. 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_availability is provided by the Mcp Calendly MCP server (shwetank-dev/mcp-server-calendly). 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 →