confirm_create_event · Google MCP: Risk & Policy

WHAT IT DOES

What confirm_create_event does on Google

AI agents use confirm_create_event to create or update resources in Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google environment.

WHY IT NEEDS A POLICY

Why confirm_create_event needs a policy

This tool creates a new calendar event, which is a reversible write operation. While calendar events can be deleted, the creation itself is a write action. Severity is medium because unintended calendar event creation could cause schedule confusion and coordination issues, but is not destructive or financial. The tool appears to finalize a previously prepared event, making it a deliberate write operation.

From the tool's definition Tool name contains 'create' and description states 'create the prepared calendar event', indicating data creation in Google Calendar.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_create_event Rate-limited

confirm_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "confirm_create_event": {
      "limits": [
        {
          "counter": "confirm_create_event_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google, so you can run agents against it safely.

FAQ

Questions about confirm_create_event

What does the confirm_create_event tool do? +

✅ Confirm and create the prepared calendar event. It is categorised as a Write tool in the Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on confirm_create_event? +

Register the Google MCP server in PolicyLayer and add a rule for confirm_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. Nothing to install.

What risk level is confirm_create_event? +

confirm_create_event is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit confirm_create_event? +

Yes. Add a rate_limit block to the confirm_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.

How do I block confirm_create_event completely? +

Set action: deny in the PolicyLayer policy for confirm_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.

What MCP server provides confirm_create_event? +

confirm_create_event is provided by the Google MCP server (robcerda/google-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.