AI agents use create_event to create or update resources in Google Calendar MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Calendar MCP Server environment.
create_event performs a reversible write operation: it adds a new calendar entry. While it modifies the user's calendar state, the action can be undone (via delete_event). The severity is medium because misuse could create unwanted calendar events that clutter the schedule or trigger notifications/meetings, but the impact is contained and reversible.
From the tool's definition Tool description states 'Create a new calendar event' — a write operation that adds new data to the calendar. Sibling tools include 'delete_event' (Destructive) and 'update_event' (Write), confirming this server spans multiple categories.
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 Google Calendar MCP Server, 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 a new calendar event. It is categorised as a Write tool in the Google Calendar MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Calendar MCP Server 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 Google Calendar MCP Server. 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 Google Calendar MCP Server MCP server (v-3/google-calendar). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 Google Calendar MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
5 Google Calendar MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.