GOOGLESUPER_DELETE_PERMISSION
Deletes a permission from a file by permission ID. Use when you need to revoke access for a specific user or group from a file.
This record as markdown: /tools/googlesuper/googlesuper-delete-permission.md
What GOOGLESUPER_DELETE_PERMISSION does on Google Super
AI agents call GOOGLESUPER_DELETE_PERMISSION to permanently remove resources in Google Super, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
file_id | string | — | The ID of the file or shared drive. |
permission_id | string | — | The ID of the permission. |
supportsAllDrives | boolean | — | Whether the requesting application supports both My Drives and shared drives. |
useDomainAdminAccess | boolean | — | Issue the request as a domain administrator; if set to true, then the requester will be granted access if the file ID parameter refers to a shared drive and the |
Parameters from the server's own tool schema.
Why GOOGLESUPER_DELETE_PERMISSION is rated Critical
Deleting permissions is an irreversible action that cannot be undone without manually re-adding the permission. While not destroying the file itself, it permanently revokes access for users/groups, making this a destructive operation on access control metadata.
From the tool's definition Tool name contains 'DELETE' and description states 'Deletes a permission from a file' — this irreversibly removes access control settings.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_DELETE_PERMISSION 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_DELETE_PERMISSION, this is the rule to start with:
GOOGLESUPER_DELETE_PERMISSION is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_DELETE_PERMISSION call is checked against it from then on.
Questions about GOOGLESUPER_DELETE_PERMISSION
Deletes a permission from a file by permission ID. Use when you need to revoke access for a specific user or group from a file. It is categorised as a Destructive tool in the Google Super MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
GOOGLESUPER_DELETE_PERMISSION accepts 4 parameters: file_id, permission_id, supportsAllDrives, useDomainAdminAccess. The full parameter table on this page comes from the server's own tool schema.
Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_DELETE_PERMISSION: 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.
GOOGLESUPER_DELETE_PERMISSION is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the GOOGLESUPER_DELETE_PERMISSION 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.
Set action: deny in the PolicyLayer policy for GOOGLESUPER_DELETE_PERMISSION. 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.
GOOGLESUPER_DELETE_PERMISSION 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.
More on Google Super, and thousands of servers like it.
Across the catalogue