reinstall_wordpress

Reinstall WordPress on a hosting package

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/reinstall-wordpress.md

WHAT IT DOES

What reinstall_wordpress does on 20i MCP Server

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

Reinstalling WordPress is a destructive operation that irreversibly overwrites the existing WordPress installation. This would destroy all custom themes, plugins, configurations, and potentially wipe or reset the database. There is no way to recover the previous state without a prior backup, making this a critical destructive action.

From the tool's definition 'Reinstall WordPress' — reinstalling WordPress overwrites existing WordPress installation, destroying all customizations, themes, plugins, and potentially database content irreversibly

Attacks that exploit this kind of access

RECOMMENDED RULE

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

reinstall_wordpress Hidden

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

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 reinstall_wordpress call is checked against it from then on.

FAQ

Questions about reinstall_wordpress

What does the reinstall_wordpress tool do? +

Reinstall WordPress on a hosting package. 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 reinstall_wordpress? +

Register the 20i MCP Server MCP server in PolicyLayer and add a rule for reinstall_wordpress: 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 reinstall_wordpress? +

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

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

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

reinstall_wordpress 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 →