calendar_set_event_reminders · Google MCP: Risk & Policy

WHAT IT DOES

What calendar_set_event_reminders does on Google

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

This tool modifies existing calendar event metadata (reminders) reversibly. It does not create events (would be Write but without existing modification), delete events (Destructive), or execute arbitrary code (Execute). The blast radius is medium because misconfigured reminders could cause notification spam or missed alerts, but changes are easily reversible via updating reminders again.

From the tool's definition Tool name 'calendar_set_event_reminders' and description indicate modification of event properties (reminders) rather than creation or deletion. The JSON format example shows parameterized configuration of reminder settings.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calendar_set_event_reminders Rate-limited

calendar_set_event_reminders 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": {
    "calendar_set_event_reminders": {
      "limits": [
        {
          "counter": "calendar_set_event_reminders_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 calendar_set_event_reminders

What does the calendar_set_event_reminders tool do? +

Set reminders for an event (JSON format: [{"method": "email", "minutes": 30}]). 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 calendar_set_event_reminders? +

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

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

Can I rate-limit calendar_set_event_reminders? +

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

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

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