New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete_content_control

Remove an SDT content control wrapper, keeping its content in place.

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-content-control.md

What delete_content_control does on Docx

AI agents call delete_content_control 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_content_control is rated Critical

This tool performs irreversible deletion of document structural elements (content controls/SDTs). Although content is retained, the removal of the wrapper cannot be undone through normal document operations and alters the document's structure permanently. This qualifies as Destructive rather than Write due to the irreversible nature of structural manipulation.

From the tool's definition Tool name 'delete_content_control' and description 'Remove an SDT content control wrapper' indicate irreversible deletion of document structure elements.

Questions about delete_content_control

What does the delete_content_control tool do? +

Remove an SDT content control wrapper, keeping its content in place. 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_content_control? +

Register the Docx MCP server in PolicyLayer and add a rule for delete_content_control: 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_content_control? +

delete_content_control 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_content_control? +

Yes. Add a rate_limit block to the delete_content_control 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_content_control completely? +

Set action: deny in the PolicyLayer policy for delete_content_control. 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_content_control? +

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

More on Docx, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Docx's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.