Add a new column to every row of a table. First row gets header_text.
AI agents use add_column_to_table to create or update resources in Docx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docx environment.
This tool creates new structural elements within a Word document table by adding columns. It is a reversible modification operation that changes document content without deleting or irreversibly destroying data. Severity is medium because misuse could corrupt document formatting or introduce unwanted structural changes, but the impact is localized to a single table and easily reversible.
From the tool's definition Tool description states 'Add a new column to every row of a table', which modifies document structure. The sibling tools include write operations like 'add_comment', 'add_bookmark', 'add_content_control', and 'add_endnote', confirming this server's Write…
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access add_column_to_table gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx, and nothing reaches the server without passing your rules. This is the rule we recommend for add_column_to_table:
{
"version": "1",
"default": "deny",
"tools": {
"add_column_to_table": {
"limits": [
{
"counter": "add_column_to_table_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_column_to_table 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.
Free to start. No card required.
Add a new column to every row of a table. First row gets header_text. It is categorised as a Write tool in the Docx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docx MCP server in PolicyLayer and add a rule for add_column_to_table: 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 Docx. Nothing to install.
add_column_to_table 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 add_column_to_table 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 add_column_to_table. 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.
add_column_to_table is provided by the Docx MCP server (securityronin/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
219 Docx tools catalogued and risk-classified — across an index of 43,000+ MCP servers.