GOOGLESUPER_GET_DOCUMENT_BY_ID
Retrieves an existing Google Document by its ID; will error if the document is not found.
This record as markdown: /tools/googlesuper/googlesuper-get-document-by-id.md
What GOOGLESUPER_GET_DOCUMENT_BY_ID does on Google Super
AI agents call GOOGLESUPER_GET_DOCUMENT_BY_ID 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 |
|---|---|---|---|
id | string | — | The unique identifier for the Google Document to be retrieved. This action specifically fetches an existing document and will not create a new one if the ID is |
Parameters from the server's own tool schema.
Why GOOGLESUPER_GET_DOCUMENT_BY_ID is rated Low
This tool performs a simple retrieval operation on a Google Document. It queries data by ID and returns it without modifying, deleting, or executing any code. The error handling described indicates defensive behavior typical of read operations. No financial, destructive, or execution capabilities are present.
From the tool's definition Tool name and description: 'Retrieves an existing Google Document by its ID'; core action is retrieval with no modification or deletion stated. The phrase 'will error if the document is not found' indicates a safe query operation with no side effects.
Attacks that exploit this kind of access
The rule that runs GOOGLESUPER_GET_DOCUMENT_BY_ID 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_DOCUMENT_BY_ID, this is the rule to start with:
GOOGLESUPER_GET_DOCUMENT_BY_ID 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_DOCUMENT_BY_ID call is checked against it from then on.
Questions about GOOGLESUPER_GET_DOCUMENT_BY_ID
Retrieves an existing Google Document by its ID; will error if the document is not found. It is categorised as a Read tool in the Google Super MCP Server, which means it retrieves data without modifying state.
GOOGLESUPER_GET_DOCUMENT_BY_ID accepts 1 parameter: 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_GET_DOCUMENT_BY_ID: 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_DOCUMENT_BY_ID 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_DOCUMENT_BY_ID 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_DOCUMENT_BY_ID. 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_DOCUMENT_BY_ID 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