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.

SERVERGoogle Super SOURCEgooglesuper
Medium RISK CLASS
Category Write
Parameters 10 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Questions about GOOGLESUPER_HIDE_DRIVE

What does the GOOGLESUPER_HIDE_DRIVE tool do? +

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.

What parameters does GOOGLESUPER_HIDE_DRIVE accept? +

GOOGLESUPER_HIDE_DRIVE accepts 1 parameter: drive_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_HIDE_DRIVE? +

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.

What risk level is GOOGLESUPER_HIDE_DRIVE? +

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

Can I rate-limit GOOGLESUPER_HIDE_DRIVE? +

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.

How do I block GOOGLESUPER_HIDE_DRIVE completely? +

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.

What MCP server provides GOOGLESUPER_HIDE_DRIVE? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Super's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.