[Calendar API v3] Create a new calendar event with Google Meet conference and guest permissions
High parameter count (12 properties)
Part of the Google Calendar and Meet MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use calendar_v3_create_event to create or modify resources in Google Calendar and Meet. 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 calendar_v3_create_event repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Google Calendar and Meet.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
calendar_v3_create_event:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Google Calendar and Meet policy for all 25 tools.
Agents calling write-class tools like calendar_v3_create_event have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
[Calendar API v3] Create a new calendar event with Google Meet conference and guest permissions. It is categorised as a Write tool in the Google Calendar and Meet MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for calendar_v3_create_event. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Calendar and Meet MCP server.
calendar_v3_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 calendar_v3_create_event rule in your Intercept 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 Intercept policy for calendar_v3_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.
calendar_v3_create_event is provided by the Google Calendar and Meet MCP server (INSIDE-HAIR/mcp-google-meet-and-calendar). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept