calendar_respond_to_event · Google MCP: Risk & Policy

WHAT IT DOES

What calendar_respond_to_event does on Google

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

This tool modifies calendar state by changing the user's RSVP response to an event invitation. While reversible (the response can be changed later), it creates a persistent change to calendar data and may trigger notifications to event organizers. It does not retrieve data (Read), execute arbitrary operations (Execute), delete data permanently (Destructive), or move money (Financial).

From the tool's definition Tool name 'calendar_respond_to_event' combined with description stating it can respond with 'accepted, declined, tentative' indicates modification of calendar event attendance status.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

calendar_respond_to_event Rate-limited

calendar_respond_to_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": {
    "calendar_respond_to_event": {
      "limits": [
        {
          "counter": "calendar_respond_to_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 calendar_respond_to_event

What does the calendar_respond_to_event tool do? +

Respond to an event invitation (accepted, declined, tentative). 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_respond_to_event? +

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

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

Can I rate-limit calendar_respond_to_event? +

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

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

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