legal_put_document

Replace a whole legal document (every section not listed is gone). Sections are ordered; omit slug to derive it from the heading. The linked page

SERVERWordpress SOURCE@cavort-it-systems/wordpress-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/io-github-cvrt-jh-wordpress-mcp/legal-put-document.md

WHAT IT DOES

What legal_put_document does on Wordpress

AI agents call legal_put_document to permanently remove resources in Wordpress, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why legal_put_document is rated Critical

Unlisted sections are permanently deleted, making this irreversible destructive overwrite.

From the tool's definition Replace a whole legal document (every section not listed is gone)

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs legal_put_document safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For legal_put_document, this is the rule to start with:

legal_put_document Hidden

legal_put_document 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": [
    "legal_put_document"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about legal_put_document

What does the legal_put_document tool do? +

Replace a whole legal document (every section not listed is gone). Sections are ordered; omit slug to derive it from the heading. The linked page. It is categorised as a Destructive tool in the Wordpress 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 legal_put_document? +

Register the Wordpress MCP server in PolicyLayer and add a rule for legal_put_document: 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 Wordpress. Nothing to install.

What risk level is legal_put_document? +

legal_put_document 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 legal_put_document? +

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

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

legal_put_document is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Blast radius →Tool call approval →