wpscan_wordpress · ikaliMCP Server MCP: Risk & Policy

WHAT IT DOES

What wpscan_wordpress does on ikaliMCP Server

AI agents invoke wpscan_wordpress to trigger actions in ikaliMCP 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_wordpress needs a policy

WPScan actively probes a remote WordPress installation by sending HTTP requests to enumerate users, plugins, themes, and known vulnerabilities. This constitutes external operation execution against a target system. While it is nominally read-only from the local machine's perspective, it triggers active reconnaissance operations against a remote host.

From the tool's definition WordPress security scanner - detects vulnerabilities, themes, plugins, and users; part of a suite including hydra_bruteforce, sqlmap_injection, and other penetration testing tools

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wpscan_wordpress Rate-limited

wpscan_wordpress 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_wordpress": {
      "limits": [
        {
          "counter": "wpscan_wordpress_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 ikaliMCP Server, so you can run agents against it safely.

FAQ

Questions about wpscan_wordpress

What does the wpscan_wordpress tool do? +

WordPress security scanner - detects vulnerabilities, themes, plugins, and users. It is categorised as a Execute tool in the ikaliMCP 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_wordpress? +

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

What risk level is wpscan_wordpress? +

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

Can I rate-limit wpscan_wordpress? +

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

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

wpscan_wordpress is provided by the ikaliMCP Server MCP server (whobcode/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.