List scheduled (and canceled) meetings from your SavvyCal account. Use this to answer questions like: - "What meetings do I have this week?" - "Show me all bookings in March" - "Did anyone cancel recently?" Args: - after (string, optional): ISO 8601 date — only return events starting after ...
Part of the SavvyCal MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call savvycal_list_events 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_list_events 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_list_events:
rules:
- action: allowSee the full SavvyCal MCP Server policy for all 8 tools.
Agents calling read-class tools like savvycal_list_events 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.
List scheduled (and canceled) meetings from your SavvyCal account. Use this to answer questions like: - "What meetings do I have this week?" - "Show me all bookings in March" - "Did anyone cancel recently?" Args: - after (string, optional): ISO 8601 date — only return events starting after this date (e.g. "2026-03-01" or "2026-03-01T09:00:00Z") - before (string, optional): ISO 8601 date — only return events starting before this date - limit (number, optional): Max events to return, 1–100 (default: 20) - cursor_after (string, optional): Pagination cursor from a previous response's metadata.after field - response_format ("markdown" | "json"): Output format (default: "markdown") Returns (markdown): Formatted list of events with status, time, attendees, and join links. Returns (json): Structured data with entries array and pagination metadata. Examples: - "Show my next 5 meetings" → after=today's date, limit=5 - "List all meetings this month" → after=start of month, before=end of month. 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_list_events. 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_list_events 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_list_events 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_list_events. 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_list_events 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