insert_table_column
AI agents use insert_table_column 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.
This tool creates or modifies document content (adding a table column) without permanently deleting data or executing arbitrary code. The change is reversible through undo or deletion. While the description is empty, the tool name and server context clearly indicate Write-category functionality.
From the tool's definition Tool name 'insert_table_column' indicates modification of table structure within a Google Doc. Server description states the tool 'edit and manage Google Docs' with support for 'tables'.
Attacks that exploit this kind of access
insert_table_column. 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.
Register the Google Docs MCP Server MCP server in PolicyLayer and add a rule for insert_table_column: 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.
insert_table_column 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 insert_table_column 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 insert_table_column. 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.
insert_table_column 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.
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 →