create_meeting_from_email · Google MCP: Risk & Policy

WHAT IT DOES

What create_meeting_from_email does on Google

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

This tool creates a new calendar event based on email content. While it modifies state (adds an event to the calendar), the operation is reversible (events can be deleted). It does not execute arbitrary code, delete data, or move money. The 'medium' severity reflects that calendar event creation could generate unwanted notifications/invitations or clutter calendars, but the impact is limited and reversible.

From the tool's definition Tool description states 'create a calendar event from it', which is a create/write operation. The broader server context includes similar operations like 'calendar_create_event' and 'calendar_create_calendar', confirming this as a Write-category tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_meeting_from_email Rate-limited

create_meeting_from_email 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": {
    "create_meeting_from_email": {
      "limits": [
        {
          "counter": "create_meeting_from_email_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 create_meeting_from_email

What does the create_meeting_from_email tool do? +

Parse an email and create a calendar event from it. 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 create_meeting_from_email? +

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

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

Can I rate-limit create_meeting_from_email? +

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

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

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