Create a new event in Google Calendar
AI agents use createEvent 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.
This tool creates new calendar events, which is a reversible write operation. It does not execute arbitrary code, delete data permanently, or move money. Severity is medium because misconfigured event creation could spam calendars or create false commitments, but the effect is localized to the user's calendar and can be undone via the deleteEvent tool.
From the tool's definition Tool name 'createEvent' and description 'Create a new event in Google Calendar' directly indicate data creation. Sibling tools include 'deleteEvent' and 'updateEvent', confirming this server manages calendar data lifecycle.
Attacks that exploit this kind of access
Create a new event in Google Calendar. 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 createEvent: 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.
createEvent 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 createEvent 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 createEvent. 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.
createEvent is provided by the Google Calendar MCP Server MCP server (naotaka3/google-calendar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →