share_document · Google Docs MCP Server MCP: Risk & Policy

WHAT IT DOES

What share_document does on Google Docs MCP Server

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

WHY IT NEEDS A POLICY

Why share_document needs a policy

Sharing a document changes its permission structure and grants access to specified users, which is a write operation that modifies the document's metadata and access state. While reversible (permissions can be unshared), the blast radius is high because an AI agent could inadvertently expose sensitive documents to unauthorized parties or the wrong users, leading to data leakage or privacy violations.

From the tool's definition Tool description explicitly states 'Share a Google Document with a specific user' — this modifies the access control and sharing permissions of a document, which is a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

share_document Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "share_document": {
      "limits": [
        {
          "counter": "share_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Docs MCP Server, so you can run agents against it safely.

FAQ

Questions about share_document

What does the share_document tool do? +

Share a Google Document with a specific user. It is categorised as a Write tool in the Google Docs MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on share_document? +

Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for share_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 Docs MCP Server. Nothing to install.

What risk level is share_document? +

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

Can I rate-limit share_document? +

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

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

share_document is provided by the Google Docs MCP Server MCP server (nickweedon/google-docs-mcp-docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.