delete_field

Remove a complete complex field (begin through end runs) from the document.

SERVERDocx SOURCEsecurityronin/docx-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/securityronin-docx-mcp/delete-field.md

WHAT IT DOES

What delete_field does on Docx

AI agents call delete_field 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.

RISK

Why delete_field is rated Critical

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_field 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_field, this is the rule to start with:

delete_field Hidden

delete_field is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Docx, apply this rule, and every delete_field call is checked against it from then on.

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.

KEEP EXPLORING

More on Docx, and thousands of servers like it.

This server

All 219 Docx tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →