insert_footnote · Google Docs MCP Server MCP: Risk & Policy

WHAT IT DOES

What insert_footnote does on Google Docs MCP Server

AI agents use insert_footnote 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 insert_footnote needs a policy

Inserting a footnote into a Google Doc is a write operation that adds content to a document reversibly. While the tool description is empty (reducing confidence), the tool name and server context clearly indicate it modifies document structure. This is less severe than destructive operations and does not execute arbitrary code or involve financial transactions.

From the tool's definition Tool name 'insert_footnote' combined with server context showing tools that 'create, read, edit, and manage Google Docs' indicates this tool modifies document content. No description provided, lowering confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

insert_footnote Rate-limited

insert_footnote 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": {
    "insert_footnote": {
      "limits": [
        {
          "counter": "insert_footnote_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 insert_footnote

What does the insert_footnote tool do? +

insert_footnote. 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 insert_footnote? +

Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for insert_footnote: 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 insert_footnote? +

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

Can I rate-limit insert_footnote? +

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

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

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