Low Risk

google_docs_export_document

Export a Google Doc in various formats (PDF, TXT, HTML, DOCX)

How to control google_docs_export_document ↓

AI agents call google_docs_export_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.

Low Risk

Exporting a document is a read operation that retrieves data without side effects. The user must already have access to the document to export it. No data is created, modified, deleted, or executed—only retrieved and converted to a different format.

From the tool's definition Tool exports/retrieves document content in various formats (PDF, TXT, HTML, DOCX); no modification, deletion, or execution occurs.

Documented attack patterns abuse exactly the kind of access google_docs_export_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_export_document:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_docs_export_document": {}
  }
}

google_docs_export_document is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Sage MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the google_docs_export_document tool do? +

Export a Google Doc in various formats (PDF, TXT, HTML, DOCX). 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_export_document? +

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

What risk level is google_docs_export_document? +

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

Can I rate-limit google_docs_export_document? +

Yes. Add a rate_limit block to the google_docs_export_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.

How do I block google_docs_export_document completely? +

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

What MCP server provides google_docs_export_document? +

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

Enforce policy on every Sage MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.