fields_delete_definition

Delete a database definition. Stored field values stay in post/term/user meta and options.

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/fields-delete-definition.md

WHAT IT DOES

What fields_delete_definition does on Wordpress

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

Irreversibly deletes field definitions; cannot be undone without restoration.

From the tool's definition Delete a database definition. Stored field values stay in post/term/user meta.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

fields_delete_definition Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about fields_delete_definition

What does the fields_delete_definition tool do? +

Delete a database definition. Stored field values stay in post/term/user meta and options. 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 fields_delete_definition? +

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

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

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

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

fields_delete_definition 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

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 code and CI agents →Blast radius →Tool call approval →