AI agents use google_calendar_create_event to create or update resources in Google MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google MCP environment.
Creating a calendar event is a reversible write operation—events can be edited or deleted afterward. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because misuse could create numerous unwanted calendar entries causing calendar spam or disruption, but the blast radius is limited to calendar scheduling and can be remediated by deletion.
From the tool's definition Tool name explicitly states 'create_event' and description confirms it 'Create a new event in Google Calendar'. This is a create operation that adds new data to the calendar.
Documented attack patterns abuse exactly the kind of access google_calendar_create_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for google_calendar_create_event:
{
"version": "1",
"default": "deny",
"tools": {
"google_calendar_create_event": {
"limits": [
{
"counter": "google_calendar_create_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}google_calendar_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 Google Calendar. It is categorised as a Write tool in the Google MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google MCP server in PolicyLayer and add a rule for google_calendar_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 MCP. Nothing to install.
google_calendar_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 google_calendar_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 google_calendar_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.
google_calendar_create_event is provided by the Google MCP server (vakharwalad23/google-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google 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.
35 Google MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.