GOOGLESUPER_HIDE_DRIVE
Tool to hide a shared drive from the default view. Use when you want to remove a shared drive from the user's main Google Drive interface without deleting it.
This record as markdown: /tools/googlesuper/googlesuper-hide-drive.md
What GOOGLESUPER_HIDE_DRIVE does on Google Super
AI agents use GOOGLESUPER_HIDE_DRIVE 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 |
|---|---|---|---|
drive_id | string | — | The ID of the shared drive. |
Parameters from the server's own tool schema.
Why GOOGLESUPER_HIDE_DRIVE is rated Medium
This tool modifies the visibility/display settings of a shared drive — a reversible write operation. It explicitly states it does NOT delete the drive, so it is not Destructive. The action changes user interface state (hiding from view), which can presumably be undone by unhiding.
From the tool's definition hide a shared drive from the default view... remove a shared drive from the user's main Google Drive interface without deleting it
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_HIDE_DRIVE 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_HIDE_DRIVE, this is the rule to start with:
GOOGLESUPER_HIDE_DRIVE 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Google Super, apply this rule, and every GOOGLESUPER_HIDE_DRIVE call is checked against it from then on.
Questions about GOOGLESUPER_HIDE_DRIVE
Tool to hide a shared drive from the default view. Use when you want to remove a shared drive from the user's main Google Drive interface without deleting it. 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.
GOOGLESUPER_HIDE_DRIVE accepts 1 parameter: drive_id. 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_HIDE_DRIVE: 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_HIDE_DRIVE is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the GOOGLESUPER_HIDE_DRIVE 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_HIDE_DRIVE. 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_HIDE_DRIVE 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