delete_field

THE RISK

Critical Risk

Why delete_field needs a policy

The tool irreversibly removes document content (fields) without possibility of undo through normal operations. While document edits may theoretically be recovered via version history, the deletion action itself cannot be undone within the tool's scope, making it destructive rather than merely a write operation.

From the tool's definition Tool name 'delete_field' and description 'Remove a complete complex field (begin through end runs) from the document' explicitly perform deletion, which is irreversible.

Documented attack patterns abuse exactly the kind of access delete_field gives an agent:

POLICY

How to control delete_field

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 delete_field:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_field"
  ]
}

delete_field disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Docx — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Docx tools

Destructive delete_column_from_table Delete a column (0-based) from every row of a table. Destructive delete_comment Delete a comment and remove its range markers from the document. Destructive delete_content_control Remove an SDT content control wrapper, keeping its content in place. Destructive delete_custom_property Delete a custom document property by name. Destructive delete_endnote Delete an endnote and its in-body reference. Destructive delete_footer Delete a footer by location: default, first, or even. Destructive delete_footnote Delete a footnote and its in-body reference. Destructive delete_header Delete a header by location: default, first, or even.

All 219 Docx tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Docx → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_field

What does the delete_field tool do? +

Remove a complete complex field (begin through end runs) from the 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.

How do I enforce a policy on delete_field? +

Register the Docx MCP server in PolicyLayer and add a rule for delete_field: 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.

What risk level is delete_field? +

delete_field is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_field? +

Yes. Add a rate_limit block to the delete_field 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.

How do I block delete_field completely? +

Set action: deny in the PolicyLayer policy for delete_field. 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.

What MCP server provides delete_field? +

delete_field 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.

Enforce policy on every Docx tool call.

Start from Docx, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →