Retrieve the content of a Google Doc by its ID. Args: - document_id (string): The ID of the Google Doc (found in the URL after /d/) - response_format (
AI agents call docs_get_document to retrieve information from Google Workspace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool fetches document content by ID. It performs a read-only query operation with no capability to modify, delete, or execute code. The argument is a document identifier, not a destructive or code-execution parameter. Blast radius is minimal — unauthorized reads of docs are a confidentiality concern but carry lower risk than write, execute, or destructive operations.
From the tool's definition Tool name 'docs_get_document' and description 'Retrieve the content of a Google Doc' — both indicate retrieval of data with no side effects.
Documented attack patterns abuse exactly the kind of access docs_get_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Google Workspace, and nothing reaches the server without passing your rules. This is the rule we recommend for docs_get_document:
{
"version": "1",
"default": "deny",
"tools": {
"docs_get_document": {}
}
} docs_get_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the content of a Google Doc by its ID. Args: - document_id (string): The ID of the Google Doc (found in the URL after /d/) - response_format (. It is categorised as a Read tool in the Google Workspace MCP Server, which means it retrieves data without modifying state.
Register the Google Workspace MCP server in PolicyLayer and add a rule for docs_get_document: 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 Workspace. Nothing to install.
docs_get_document 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 docs_get_document 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 docs_get_document. 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.
docs_get_document is provided by the Google Workspace MCP server (everyinc/google-workspace-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Google Workspace, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
34 Google Workspace tools catalogued and risk-classified — across an index of 43,000+ MCP servers.