GOOGLESUPER_GENERATE_IDS

Generates a set of file IDs which can be provided in create or copy requests. Use when you need to pre-allocate IDs for new files or copies.

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-generate-ids.md

WHAT IT DOES

What GOOGLESUPER_GENERATE_IDS does on Google Super

AI agents use GOOGLESUPER_GENERATE_IDS 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
`type`	string	—	The type of items for which the IDs can be used. For example, 'files' or 'shortcuts'.
`count`	integer	—	The number of IDs to return. Value must be between 1 and 1000, inclusive.
`space`	string	—	The space in which the IDs can be used. Supported values are 'drive' and 'appDataFolder'.

Parameters from the server's own tool schema.

RISK

Why GOOGLESUPER_GENERATE_IDS is rated Medium

This tool generates identifiers that will be used in subsequent create or copy operations, but does not itself create, modify, delete, or execute actions. It prepares metadata (IDs) for future write operations, making it a preparatory Write-category action with low severity—misuse would at worst result in wasted ID allocations, not unintended data modification or destruction.

From the tool's definition Tool description states it 'Generates a set of file IDs' and is used to 'pre-allocate IDs for new files or copies.' The term 'pre-allocate' indicates reservation of identifiers rather than actual creation or modification of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs GOOGLESUPER_GENERATE_IDS 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_GENERATE_IDS, this is the rule to start with:

GOOGLESUPER_GENERATE_IDS Rate-limited

GOOGLESUPER_GENERATE_IDS 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_GENERATE_IDS": {
      "limits": [
        {
          "counter": "googlesuper_generate_ids_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_GENERATE_IDS call is checked against it from then on.

FAQ

Questions about GOOGLESUPER_GENERATE_IDS

What does the GOOGLESUPER_GENERATE_IDS tool do? +

Generates a set of file IDs which can be provided in create or copy requests. Use when you need to pre-allocate IDs for new files or copies. 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_GENERATE_IDS accept? +

GOOGLESUPER_GENERATE_IDS accepts 3 parameters: type, count, space. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on GOOGLESUPER_GENERATE_IDS? +

Register the Google Super MCP server in PolicyLayer and add a rule for GOOGLESUPER_GENERATE_IDS: 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_GENERATE_IDS? +

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

Can I rate-limit GOOGLESUPER_GENERATE_IDS? +

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

Set action: deny in the PolicyLayer policy for GOOGLESUPER_GENERATE_IDS. 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_GENERATE_IDS? +

GOOGLESUPER_GENERATE_IDS 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

generate_commit on MCP Server PR Pilot →generate_video_title on YouTube MCP Server →generate_devtools_report on Percepta MCP Server →generate_evidence_manifest on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

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