gcal_create_event · Integrations MCP: Risk & Policy

WHAT IT DOES

What gcal_create_event does on Integrations MCP

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

WHY IT NEEDS A POLICY

Why gcal_create_event needs a policy

This tool creates calendar events, a reversible write operation. Severity is medium because an AI agent could spam calendar invitations, clutter calendars, or create misleading events that disrupt workflows, but the impact is contained to calendar data and not destructive, financial, or system-critical.

From the tool's definition Tool name is 'gcal_create_event', which creates a calendar event in Google Calendar. The 'create' verb and Google Calendar context indicate data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gcal_create_event Rate-limited

gcal_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": {
    "gcal_create_event": {
      "limits": [
        {
          "counter": "gcal_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 Integrations MCP, so you can run agents against it safely.

FAQ

Questions about gcal_create_event

What does the gcal_create_event tool do? +

gcal_create_event. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gcal_create_event? +

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

What risk level is gcal_create_event? +

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

Can I rate-limit gcal_create_event? +

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

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

gcal_create_event is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.