This record as markdown: /tools/andrew82106-llm-docx-agent-mcp/delete-docx.md
What delete_docx does on Docx
AI agents call delete_docx to permanently remove resources in Docx, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_docx is rated Critical
This tool performs an irreversible deletion operation that cannot be undone. Deletion of documents is the canonical example of a Destructive action. The severity is high because loss of a Word document can represent significant data loss depending on content, though not universally critical (unlike financial transactions). High confidence because the intent is unambiguous.
From the tool's definition Tool name 'delete_docx' and description 'Delete a Word document' indicate irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_docx safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_docx, this is the rule to start with:
delete_docx is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every delete_docx call is checked against it from then on.
Questions about delete_docx
Delete a Word document. It is categorised as a Destructive tool in the Docx 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_docx: 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.
delete_docx 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_docx 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_docx. 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_docx is provided by the Docx MCP server (andrew82106/llm_docx_agent_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docx, and thousands of servers like it.
Across the catalogue