Critical Risk →

GOOGLECALENDAR_REMOVE_ATTENDEE

Removes an attendee from a specified event in a Google Calendar; the calendar and event must exist.

Part of the Google Calendar MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

google-cal-mcp Destructive Risk 4/5

AI agents may call GOOGLECALENDAR_REMOVE_ATTENDEE to permanently remove or destroy resources in Google Calendar. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call GOOGLECALENDAR_REMOVE_ATTENDEE in a loop, permanently destroying resources in Google Calendar. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

google-calendar.yaml
tools:
  GOOGLECALENDAR_REMOVE_ATTENDEE:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Google Calendar policy for all 29 tools.

Tool Name GOOGLECALENDAR_REMOVE_ATTENDEE
Category Destructive
Risk Level Critical

View all 29 tools →

Agents calling destructive-class tools like GOOGLECALENDAR_REMOVE_ATTENDEE have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

GOOGLECALENDAR_REMOVE_ATTENDEE is one of the critical-risk operations in Google Calendar. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

What does the GOOGLECALENDAR_REMOVE_ATTENDEE tool do? +

Removes an attendee from a specified event in a Google Calendar; the calendar and event must exist.. It is categorised as a Destructive tool in the Google Calendar MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on GOOGLECALENDAR_REMOVE_ATTENDEE? +

Add a rule in your Intercept YAML policy under the tools section for GOOGLECALENDAR_REMOVE_ATTENDEE. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Google Calendar MCP server.

What risk level is GOOGLECALENDAR_REMOVE_ATTENDEE? +

GOOGLECALENDAR_REMOVE_ATTENDEE is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit GOOGLECALENDAR_REMOVE_ATTENDEE? +

Yes. Add a rate_limit block to the GOOGLECALENDAR_REMOVE_ATTENDEE rule in your Intercept 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 GOOGLECALENDAR_REMOVE_ATTENDEE completely? +

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

GOOGLECALENDAR_REMOVE_ATTENDEE is provided by the Google Calendar MCP server (google-cal-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Google Calendar

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.