google_docs_read_document_content

Read the full content of a Google Doc as structured text

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/google-docs-read-document-content.md

WHAT IT DOES

What google_docs_read_document_content does on Sage MCP

AI agents call google_docs_read_document_content to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why google_docs_read_document_content is rated Low

This tool retrieves and queries data from a Google Doc without creating, modifying, deleting, or executing any operations. It is a straightforward read-only operation that returns existing data in a structured format. No side effects or irreversible changes are possible.

From the tool's definition Tool name contains 'read' and description states 'Read the full content of a Google Doc as structured text' - a pure retrieval operation with no modification capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs google_docs_read_document_content safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For google_docs_read_document_content, this is the rule to start with:

google_docs_read_document_content Allowed

google_docs_read_document_content is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_docs_read_document_content": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every google_docs_read_document_content call is checked against it from then on.

FAQ

Questions about google_docs_read_document_content

What does the google_docs_read_document_content tool do? +

Read the full content of a Google Doc as structured text. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on google_docs_read_document_content? +

Register the Sage MCP server in PolicyLayer and add a rule for google_docs_read_document_content: 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.

What risk level is google_docs_read_document_content? +

google_docs_read_document_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit google_docs_read_document_content? +

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

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

google_docs_read_document_content 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.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

read_input_file on 0gzk →claude_read_file on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →