GOOGLESUPER_REMOVE_ATTENDEE

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

SERVERGoogle Super SOURCEgooglesuper

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/googlesuper/googlesuper-remove-attendee.md

WHAT IT DOES

What GOOGLESUPER_REMOVE_ATTENDEE does on Google Super

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

Parameter	Type	Required	Description
`event_id`	string	—	Unique identifier of the event.
`calendar_id`	string	—	Identifier of the Google Calendar to which the event belongs; 'primary' signifies the user's main calendar.
`attendee_email`	string	—	Email address of the attendee to remove. Must match an attendee email present on the event.

Parameters from the server's own tool schema.

RISK

Why GOOGLESUPER_REMOVE_ATTENDEE is rated Medium

Removing an attendee modifies an existing calendar event by changing its attendee list. This is a reversible write operation (the attendee could be re-added), not a deletion of the event itself. Misuse could disrupt meeting coordination but is not irreversible.

From the tool's definition Removes an attendee from a specified event in a Google Calendar

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GOOGLESUPER_REMOVE_ATTENDEE safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Google Super, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For GOOGLESUPER_REMOVE_ATTENDEE, this is the rule to start with:

GOOGLESUPER_REMOVE_ATTENDEE Rate-limited

GOOGLESUPER_REMOVE_ATTENDEE 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": {
    "GOOGLESUPER_REMOVE_ATTENDEE": {
      "limits": [
        {
          "counter": "googlesuper_remove_attendee_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_REMOVE_ATTENDEE call is checked against it from then on.

FAQ

Questions about GOOGLESUPER_REMOVE_ATTENDEE

What does the GOOGLESUPER_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 Write tool in the Google Super MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does GOOGLESUPER_REMOVE_ATTENDEE accept? +

GOOGLESUPER_REMOVE_ATTENDEE accepts 3 parameters: event_id, calendar_id, attendee_email. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_REMOVE_ATTENDEE? +

Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_REMOVE_ATTENDEE: 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 Super. Nothing to install.

What risk level is GOOGLESUPER_REMOVE_ATTENDEE? +

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

Can I rate-limit GOOGLESUPER_REMOVE_ATTENDEE? +

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

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

GOOGLESUPER_REMOVE_ATTENDEE is provided by the Google Super MCP server (googlesuper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Google Super, and thousands of servers like it.

This server

All 200 Google Super tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →