AI agents call delete_table_row to permanently remove resources in Docx_MCP_cj — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes table rows without reversibility. While the scope is limited to a single document table row rather than an entire database, the action cannot be undone programmatically and results in data loss. This is destructive rather than merely Write (which would be reversible updates).
From the tool's definition Tool name 'delete_table_row' and description '【表格行删除工具】删除指定表格行' (Table row deletion tool - delete specified table row) explicitly performs irreversible deletion of table rows from Word documents.
Documented attack patterns abuse exactly the kind of access delete_table_row gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docx_MCP_cj, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_table_row:
{
"version": "1",
"default": "deny",
"hide": [
"delete_table_row"
]
}delete_table_row 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.
【表格行删除工具】删除指定表格行. It is categorised as a Destructive tool in the Docx_MCP_cj MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Docx_MCP_cj MCP server in PolicyLayer and add a rule for delete_table_row: 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_cj. Nothing to install.
delete_table_row 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_row 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_row. 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_row is provided by the Docx_MCP_cj MCP server (rockcj/docx_mcp_cj). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 54 Docx_MCP_cj tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
54 Docx_MCP_cj tools catalogued and risk-classified — across an index of 42,500+ MCP servers.