Create a Google Calendar event using start_datetime plus event_duration_hour and event_duration_minutes fields to derive the end time. Requires calendar write access. The organizer is added as an attendee unless exclude_organizer is True. Example request to create event for 1 hour 30 minutes: { "...
Risk signalsHigh parameter count (23 properties)
Part of the Google Calendar server.
Free to start. No card required.
AI agents use GOOGLECALENDAR_CREATE_EVENT to create or modify resources in Google Calendar. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call GOOGLECALENDAR_CREATE_EVENT repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Google Calendar.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"GOOGLECALENDAR_CREATE_EVENT": {
"limits": [
{
"counter": "googlecalendar_create_event_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Google Calendar policy for all 29 tools.
These attack patterns abuse exactly the kind of access GOOGLECALENDAR_CREATE_EVENT gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Create a Google Calendar event using start_datetime plus event_duration_hour and event_duration_minutes fields to derive the end time. Requires calendar write access. The organizer is added as an attendee unless exclude_organizer is True. Example request to create event for 1 hour 30 minutes: { "calendar_id": "primary", "start_datetime": "2025-01-16T13:00:00", "timezone": "America/New_York", "event_duration_hour": 1, "event_duration_minutes": 30, "summary": "Client sync", "attendees": [{"email": "guest@example.com"}] }. It is categorised as a Write tool in the Google Calendar MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Calendar MCP server in PolicyLayer and add a rule for GOOGLECALENDAR_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. Nothing to install.
GOOGLECALENDAR_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 GOOGLECALENDAR_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 GOOGLECALENDAR_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.
GOOGLECALENDAR_CREATE_EVENT is provided by the Google Calendar MCP server (google-cal-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 29 Google Calendar tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.