check_calendar_availability
Check available booking slots for a public calendar event in Sanka.
This record as markdown: /tools/sankahq-sanka-mcp/check-calendar-availability.md
What check_calendar_availability does on Sanka MCP Server
AI agents call check_calendar_availability to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why check_calendar_availability is rated Low
This tool performs a read-only query to check availability on a public calendar. It retrieves information about booking slots without creating, modifying, deleting, or executing any operations. The blast radius is minimal—misuse would only expose calendar availability information, which is typically intended to be public. No financial, destructive, or executable side effects are present.
From the tool's definition Tool name 'check_calendar_availability' and description 'Check available booking slots for a public calendar event' indicate a query operation that retrieves calendar data without modifying, executing code, or affecting system state.
Attacks that exploit this kind of access
The rule that runs check_calendar_availability safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_calendar_availability, this is the rule to start with:
check_calendar_availability is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every check_calendar_availability call is checked against it from then on.
Questions about check_calendar_availability
Check available booking slots for a public calendar event in Sanka. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for check_calendar_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 Sanka MCP Server. Nothing to install.
check_calendar_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_calendar_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_calendar_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_calendar_availability is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue