AI agents use create_event to create or update resources in Fantastical MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fantastical MCP environment.
The tool creates calendar events, which is a reversible write operation. It does not delete or overwrite existing data (would be Destructive), execute arbitrary code (would be Execute), or involve financial transactions (would be Financial).
From the tool's definition Tool name 'create_event' combined with server description stating 'create Fantastical calendar events'. The description is empty, but the sibling tools (all read-only: get_availability, get_calendars, get_event, etc.) establish context that this tool performs…
Documented attack patterns abuse exactly the kind of access create_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Fantastical MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_event:
{
"version": "1",
"default": "deny",
"tools": {
"create_event": {
"limits": [
{
"counter": "create_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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_event. It is categorised as a Write tool in the Fantastical MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fantastical MCP server in PolicyLayer and add a rule for 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 Fantastical MCP. Nothing to install.
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 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 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.
create_event is provided by the Fantastical MCP server (jaydenk/fantastical-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Fantastical MCP, 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.
16 Fantastical MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.