AI agents call delete_table_rows to permanently remove resources in DOCX-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of table rows is irreversible—once rows are removed from a Word document, the data cannot be recovered through the tool's normal operation. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' While the blast radius is somewhat contained (only affects specific table rows within a document, not system-wide), the severity remains high…
From the tool's definition Tool name 'delete_table_rows' explicitly performs deletion. Description states 'Delete rows from a table,' which is an irreversible data removal operation.
Documented attack patterns abuse exactly the kind of access delete_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 delete_table_rows:
{
"version": "1",
"default": "deny",
"hide": [
"delete_table_rows"
]
}delete_table_rows disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete rows from a table. It is categorised as a Destructive tool in the DOCX-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DOCX- MCP server in PolicyLayer and add a rule for delete_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.
delete_table_rows is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.