Create a footer in the document. Returns the footer ID for inserting content.
AI agents use gdoc_create_footer to create or update resources in Google Docs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Docs environment.
This tool creates (inserts) a new footer section into a Google Doc, which is a reversible write operation. It does not execute arbitrary code, delete data permanently, or move money. While footers affect document layout, the action is modifiable and undoable via standard Google Docs undo/deletion mechanisms.
From the tool's definition Tool name 'gdoc_create_footer' and description 'Create a footer in the document' — the verb 'Create' indicates data creation/modification. Returns a footer ID for subsequent content insertion, confirming reversible modification of document structure.
Attacks that exploit this kind of access
Create a footer in the document. Returns the footer ID for inserting content. It is categorised as a Write tool in the Google Docs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Docs MCP server in PolicyLayer and add a rule for gdoc_create_footer: 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. Nothing to install.
gdoc_create_footer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gdoc_create_footer 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.
Set action: deny in the PolicyLayer policy for gdoc_create_footer. 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.
gdoc_create_footer is provided by the Google Docs MCP server (node2flow-th/google-docs-mcp-community). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →