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