wordpress_update_plugin_status · ItchWP MCP: Risk & Policy

WHAT IT DOES

What wordpress_update_plugin_status does on ItchWPMCP

AI agents invoke wordpress_update_plugin_status to trigger actions in ItchWPMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why wordpress_update_plugin_status needs a policy

Activating or deactivating a WordPress plugin triggers external code execution on the server. Activating a plugin runs its initialization code, and deactivating it removes active functionality. This is not a simple data write — it controls what code runs on the WordPress instance. Misuse could activate malicious plugins or disable critical security/functionality plugins, making this a high-severity Execute action.

From the tool's definition Activate or deactivate an installed plugin if the authenticated user has permission

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_update_plugin_status Rate-limited

wordpress_update_plugin_status stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wordpress_update_plugin_status": {
      "limits": [
        {
          "counter": "wordpress_update_plugin_status_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ItchWPMCP, so you can run agents against it safely.

FAQ

Questions about wordpress_update_plugin_status

What does the wordpress_update_plugin_status tool do? +

Activate or deactivate an installed plugin if the authenticated user has permission. It is categorised as a Execute tool in the ItchWPMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wordpress_update_plugin_status? +

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

What risk level is wordpress_update_plugin_status? +

wordpress_update_plugin_status is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit wordpress_update_plugin_status? +

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

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

wordpress_update_plugin_status is provided by the ItchWP MCP server (manofsadness/itchwpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.