Medium Risk

google_docs_create_document

Create a new Google Doc with optional initial content

How to control google_docs_create_document ↓

AI agents use google_docs_create_document to create or update resources in Sage MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.

Medium Risk

This tool creates a new document in Google Docs, which is a reversible write operation. It does not delete or overwrite existing data, nor does it execute code or involve financial transactions. Misuse could result in unwanted documents being created in a user's Google Drive, but the impact is moderate and reversible.

From the tool's definition 'Create a new Google Doc with optional initial content'

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "google_docs_create_document": {
      "limits": [
        {
          "counter": "google_docs_create_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

google_docs_create_document stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. 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.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the google_docs_create_document tool do? +

Create a new Google Doc with optional initial content. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on google_docs_create_document? +

Register the Sage MCP server in PolicyLayer and add a rule for google_docs_create_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_create_document? +

google_docs_create_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit google_docs_create_document? +

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

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

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