smart_create_event_unsafe · Google MCP: Risk & Policy

WHAT IT DOES

What smart_create_event_unsafe does on Google

AI agents use smart_create_event_unsafe 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 smart_create_event_unsafe needs a policy

This tool creates calendar events, which is a reversible modification of data (Write category). Severity is high because: (1) it operates without confirmation, creating potential for unintended calendar pollution or social engineering attacks if an agent is manipulated into calling it; (2) it accepts 'names or emails' as parameters, expanding the blast radius to potentially invite unintended participants; (3) the…

From the tool's definition Tool name contains 'create_event' and description states 'Create calendar event immediately without confirmation'. The ⚠️ UNSAFE warning and 'immediately without confirmation' language indicates it bypasses safety checks.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

smart_create_event_unsafe Rate-limited

smart_create_event_unsafe 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": {
    "smart_create_event_unsafe": {
      "limits": [
        {
          "counter": "smart_create_event_unsafe_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 smart_create_event_unsafe

What does the smart_create_event_unsafe tool do? +

⚠️ UNSAFE: Create calendar event immediately without confirmation (use names or emails). 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 smart_create_event_unsafe? +

Register the Google MCP server in PolicyLayer and add a rule for smart_create_event_unsafe: 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 smart_create_event_unsafe? +

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

Can I rate-limit smart_create_event_unsafe? +

Yes. Add a rate_limit block to the smart_create_event_unsafe 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 smart_create_event_unsafe completely? +

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

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