wpscan_scan · Echo MCP Server MCP: Risk & Policy

WHAT IT DOES

What wpscan_scan does on Echo MCP Server

AI agents invoke wpscan_scan to trigger actions in Echo MCP Server. 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 wpscan_scan needs a policy

WPScan is an active vulnerability scanner that probes WordPress sites for security weaknesses. It sends network requests to external targets, enumerates plugins/themes, and may attempt credential attacks. This constitutes executing an external security tool against a target system. Misuse could result in unauthorized scanning of third-party sites, potentially violating laws (CFAA, etc.) or causing disruption.

From the tool's definition Scan WordPress sites for vulnerabilities using WPScan

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wpscan_scan Rate-limited

wpscan_scan 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": {
    "wpscan_scan": {
      "limits": [
        {
          "counter": "wpscan_scan_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 Echo MCP Server, so you can run agents against it safely.

FAQ

Questions about wpscan_scan

What does the wpscan_scan tool do? +

Scan WordPress sites for vulnerabilities using WPScan. It is categorised as a Execute tool in the Echo MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on wpscan_scan? +

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

What risk level is wpscan_scan? +

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

Can I rate-limit wpscan_scan? +

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

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

wpscan_scan is provided by the Echo MCP Server MCP server (somacaru/mcp_setup). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.