GOOGLESUPER_GET_PERMISSION
Gets a permission by ID. Use this tool to retrieve a specific permission for a file or shared drive.
This record as markdown: /tools/googlesuper/googlesuper-get-permission.md
What GOOGLESUPER_GET_PERMISSION does on Google Super
AI agents call GOOGLESUPER_GET_PERMISSION to retrieve information from Google Super without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
fields | string | — | Selector specifying which fields to include in a partial response. Use 'fields=*' to return all available fields for the permission resource. |
file_id | string | — | The ID of the file. |
permission_id | string | — | The ID of the permission. |
supports_all_drives | boolean | — | Whether the requesting application supports both My Drives and shared drives. |
use_domain_admin_access | 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_GET_PERMISSION is rated Low
This tool retrieves permission metadata for files or shared drives without modifying, creating, or deleting any data. It has no side effects and poses minimal risk even if an AI agent calls it with arbitrary inputs, as the worst case is exposing already-accessible permission information.
From the tool's definition Tool name contains 'GET' and description states 'retrieve a specific permission' with no mention of modification, creation, or deletion. The action is purely informational—querying existing permission data.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_GET_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_GET_PERMISSION, this is the rule to start with:
GOOGLESUPER_GET_PERMISSION is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_GET_PERMISSION call is checked against it from then on.
Questions about GOOGLESUPER_GET_PERMISSION
Gets a permission by ID. Use this tool to retrieve a specific permission for a file or shared drive. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_GET_PERMISSION accepts 5 parameters: fields, file_id, permission_id, supports_all_drives, use_domain_admin_access. 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_GET_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_GET_PERMISSION is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the GOOGLESUPER_GET_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_GET_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_GET_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.
This server
Across the catalogue