AI agents use add_table_rows to create or update resources in DOCX-MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DOCX-MCP environment.
Adding table rows is a Write operation: it creates new content and modifies document structure reversibly. An AI agent misusing this could bloat documents or inject unwanted data, but the change is undoable (via undo or deletion). It does not execute code, delete permanently, or move money, so Write is the appropriate category.
From the tool's definition Tool name 'add_table_rows' indicates insertion of table rows into a Word document. Server description confirms 'table operations including creation, data management, formatting, and bulk operations' and 'document editing'.
Documented attack patterns abuse exactly the kind of access add_table_rows gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DOCX-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for add_table_rows:
{
"version": "1",
"default": "deny",
"tools": {
"add_table_rows": {
"limits": [
{
"counter": "add_table_rows_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_table_rows 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_table_rows. It is categorised as a Write tool in the DOCX-MCP 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_table_rows: 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-MCP. Nothing to install.
add_table_rows 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_table_rows 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_table_rows. 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_table_rows is provided by the DOCX- MCP server (rookie0x80/docx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DOCX-MCP, 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.
16 DOCX-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.