manage_wordpress_plugin

Activate, deactivate, or remove WordPress plugin

SERVER20i MCP Server SOURCEcbrown35/20i-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/cbrown35-20i-mcp/manage-wordpress-plugin.md

WHAT IT DOES

What manage_wordpress_plugin does on 20i MCP Server

AI agents call manage_wordpress_plugin to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why manage_wordpress_plugin is rated Critical

The 'remove' action is irreversible — permanently deleting a WordPress plugin cannot be undone without reinstallation and potential data loss. Per the severity rules, when a tool spans categories (Write for activate/deactivate, Destructive for remove), we pick the most severe: Destructive.

From the tool's definition Activate, deactivate, or remove WordPress plugin

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs manage_wordpress_plugin safely

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

manage_wordpress_plugin Hidden

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every manage_wordpress_plugin call is checked against it from then on.

FAQ

Questions about manage_wordpress_plugin

What does the manage_wordpress_plugin tool do? +

Activate, deactivate, or remove WordPress plugin. It is categorised as a Destructive tool in the 20i MCP Server 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 manage_wordpress_plugin? +

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

What risk level is manage_wordpress_plugin? +

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

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

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

manage_wordpress_plugin is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server tools → Critical-risk tools on this server →

Across the catalogue

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

Guides

Govern database agents →Blast radius →Tool call approval →