Get detailed metadata about a specific Google Doc
AI agents call google_docs_get_document to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata from a Google Doc without creating, modifying, deleting, or executing anything. It is a read-only query operation with minimal blast radius even if misused by an agent, as it only exposes information the authenticated user already has access to.
From the tool's definition Tool name contains 'get_document' and description states 'Get detailed metadata about a specific Google Doc' — pure retrieval with no modification, deletion, or execution.
Documented attack patterns abuse exactly the kind of access google_docs_get_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for google_docs_get_document:
{
"version": "1",
"default": "deny",
"tools": {
"google_docs_get_document": {}
}
}google_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.
Get detailed metadata about a specific Google Doc. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for google_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 Sage MCP. Nothing to install.
google_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 google_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 google_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.
google_docs_get_document is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.