extract_plugin · WordPress Plugin Directory MCP Server MCP

WHAT IT DOES

What extract_plugin does on WordPress Plugin Directory MCP Server

AI agents use extract_plugin to create or update resources in WordPress Plugin Directory MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress Plugin Directory MCP Server environment.

WHY IT NEEDS A POLICY

Why extract_plugin needs a policy

Extracting a ZIP file creates new files/directories on the local filesystem. This is a reversible write operation (extracted files can be deleted), not destructive. The blast radius is medium since it writes potentially many files to disk, but it does not execute code or delete data.

From the tool's definition Extract a downloaded plugin ZIP file

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

extract_plugin Rate-limited

extract_plugin stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "extract_plugin": {
      "limits": [
        {
          "counter": "extract_plugin_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about extract_plugin

What does the extract_plugin tool do? +

Extract a downloaded plugin ZIP file. It is categorised as a Write tool in the WordPress Plugin Directory MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on extract_plugin? +

Register the WordPress Plugin Directory MCP Server MCP server in PolicyLayer and add a rule for extract_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 WordPress Plugin Directory MCP Server. Nothing to install.

What risk level is extract_plugin? +

extract_plugin is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit extract_plugin? +

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

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

extract_plugin is provided by the WordPress Plugin Directory MCP Server MCP server (juanma-wp/wordpress-org-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.