AI agents use caldav_create_event to create or update resources in CalDAV MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CalDAV MCP Server environment.
This tool creates new calendar events, which is reversible data modification. It falls under Write category rather than Read (which only retrieves data) or Destructive (which cannot be undone). Severity is medium because misuse could create spam, fake meetings, or disruptive calendar events, but these can be deleted and don't directly cause financial harm or system compromise.
From the tool's definition Tool name 'caldav_create_event' and description 'Create a new event in the calendar' indicate creation of calendar data. The server description confirms the tool can 'create/manage events with reminders and attendees' and handle recurring events.
Documented attack patterns abuse exactly the kind of access caldav_create_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CalDAV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for caldav_create_event:
{
"version": "1",
"default": "deny",
"tools": {
"caldav_create_event": {
"limits": [
{
"counter": "caldav_create_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}caldav_create_event stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new event in the calendar. It is categorised as a Write tool in the CalDAV MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CalDAV MCP Server MCP server in PolicyLayer and add a rule for caldav_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 CalDAV MCP Server. Nothing to install.
caldav_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 caldav_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 caldav_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.
caldav_create_event is provided by the CalDAV MCP Server MCP server (madbonez/caldav-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CalDAV MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 CalDAV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.