append_to_doc · Google Connections MCP: Risk & Policy

WHAT IT DOES

What append_to_doc does on Google Connections

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

WHY IT NEEDS A POLICY

Why append_to_doc needs a policy

Appending text to a Google Doc modifies the document but does not delete or overwrite existing content, making it a Write operation rather than Destructive. The severity is medium because: (1) modifications could affect shared documents with consequences for multiple users, (2) appended content could overwrite formatting or introduce errors, but (3) the operation is reversible through undo or manual deletion.

From the tool's definition Tool name 'append_to_doc' and description 'Append text to the end of a Google Doc' indicate modification of document content. This is a write operation that creates or modifies data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

append_to_doc Rate-limited

append_to_doc 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": {
    "append_to_doc": {
      "limits": [
        {
          "counter": "append_to_doc_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 Connections, so you can run agents against it safely.

FAQ

Questions about append_to_doc

What does the append_to_doc tool do? +

Append text to the end of a Google Doc. It is categorised as a Write tool in the Google Connections MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on append_to_doc? +

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

What risk level is append_to_doc? +

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

Can I rate-limit append_to_doc? +

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

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

append_to_doc is provided by the Google Connections MCP server (michaelzrork/google-connections-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.