Book a meeting on a SavvyCal scheduling link for a specific time slot. Use this to: - Book a meeting on behalf of someone - Schedule a meeting at a specific available slot Args: - link_slug (string, required): Scheduling link slug (e.g. "intro-call") — get from savvycal_list_scheduling_links - st...
Part of the SavvyCal MCP Server server.
Free to start. No card required.
AI agents use savvycal_create_event to create or modify resources in SavvyCal MCP Server. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call savvycal_create_event repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SavvyCal MCP Server.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"savvycal_create_event": {
"limits": [
{
"counter": "savvycal_create_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full SavvyCal MCP Server policy for all 8 tools.
These attack patterns abuse exactly the kind of access savvycal_create_event gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Book a meeting on a SavvyCal scheduling link for a specific time slot. Use this to: - Book a meeting on behalf of someone - Schedule a meeting at a specific available slot Args: - link_slug (string, required): Scheduling link slug (e.g. "intro-call") — get from savvycal_list_scheduling_links - starts_at (string, required): ISO 8601 datetime for the meeting start — must match an available slot from savvycal_get_available_slots - name (string, required): Full name of the attendee being booked - email (string, required): Email address of the attendee - description (string, optional): Optional note or message for the booking Returns: The newly created event with all details including any conferencing join link. Workflow: Use savvycal_list_scheduling_links to find the link slug, then savvycal_get_available_slots to find valid times, then this tool to book.. It is categorised as a Write tool in the SavvyCal MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SavvyCal MCP Server MCP server in PolicyLayer and add a rule for savvycal_create_event: 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 SavvyCal MCP Server. Nothing to install.
savvycal_create_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the savvycal_create_event 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 savvycal_create_event. 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_create_event is provided by the SavvyCal MCP Server MCP server (arturkoter/savvycal-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 SavvyCal MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.