Get available time slots for a scheduling link within a date range. Use this to: - Answer "when am I free for a 30-minute call next week?" - Find valid times before booking with savvycal_create_event - Show someone your open availability Args: - link_slug (string, required): Scheduling link s...
Part of the SavvyCal MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call savvycal_get_available_slots to retrieve information from SavvyCal MCP Server without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though savvycal_get_available_slots only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
savvycal_get_available_slots:
rules:
- action: allowSee the full SavvyCal MCP Server policy for all 8 tools.
Agents calling read-class tools like savvycal_get_available_slots have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Get available time slots for a scheduling link within a date range. Use this to: - Answer "when am I free for a 30-minute call next week?" - Find valid times before booking with savvycal_create_event - Show someone your open availability Args: - link_slug (string, required): Scheduling link slug (e.g. "intro-call") — get from savvycal_list_scheduling_links - after (string, optional): ISO 8601 date — show slots after this date (defaults to now) - before (string, optional): ISO 8601 date — show slots before this date - response_format ("markdown" | "json"): Output format (default: "markdown") Returns: List of available time slots with start and end times. Workflow: Use savvycal_list_scheduling_links to find the slug first, then call this tool.. It is categorised as a Read tool in the SavvyCal MCP Server MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for savvycal_get_available_slots. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SavvyCal MCP Server MCP server.
savvycal_get_available_slots 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 savvycal_get_available_slots rule in your Intercept 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 Intercept policy for savvycal_get_available_slots. 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.
savvycal_get_available_slots is provided by the SavvyCal MCP Server MCP server (arturkoter/savvycal-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept