# wpscan_scan

A execute tool on the Kali Security MCP MCP server.

Agent View of the PolicyLayer registry record for `wpscan_scan`. HTML page: https://policylayer.com/tools/seac-25-kali-security-mcp/wpscan-scan

## Facts

- Tool: `wpscan_scan`
- Server: Kali Security MCP (`seac-25/kali-security-mcp`) — https://policylayer.com/tools/seac-25-kali-security-mcp.md
- Homepage: https://github.com/SeaC-25/Kali-Security-MCP
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "wpscan_scan",
    "arguments": {}
  }
}
```

## Why wpscan_scan is rated High

WPScan is an active scanning tool that probes target WordPress installations for vulnerabilities, misconfigurations, exposed users, and weak credentials. It executes network requests against external targets, constituting an active security operation. The server context (Kali Linux pentest tooling) confirms offensive/active use. Empty description lowers confidence slightly, but the tool name is unambiguous.

From the tool's own definition: "Tool name 'wpscan_scan' references WPScan, a well-known WordPress vulnerability scanner used in penetration testing. Server description states it integrates 193 Kali Linux security tools for penetration testing and vulnerability assessment."

## Use case

AI agents invoke wpscan_scan to trigger actions in Kali Security MCP. 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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Kali Security MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "wpscan_scan": {
      "limits": [
        {
          "counter": "wpscan_scan_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Kali Security MCP (193)

- `adaptive_cmdi_test` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/adaptive-cmdi-test.md
- `adaptive_create_execution_context` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/adaptive-create-execution-context.md
- `adaptive_execute_strategy` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/adaptive-execute-strategy.md
- `adaptive_intelligent_orchestration` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/adaptive-intelligent-orchestration.md
- `adaptive_network_penetration` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/adaptive-network-penetration.md
- `adaptive_sqli_test` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/adaptive-sqli-test.md
- `adaptive_web_penetration` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/adaptive-web-penetration.md
- `adaptive_xss_test` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/adaptive-xss-test.md
- `add_chain_step` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/add-chain-step.md
- `agent_run` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/agent-run.md
- `aircrack_attack` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/aircrack-attack.md
- `apt_comprehensive_attack` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/apt-comprehensive-attack.md
- `apt_network_penetration` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/apt-network-penetration.md
- `apt_web_application_attack` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/apt-web-application-attack.md
- `arp_scan` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/arp-scan.md
- `auth_bypass_test` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/auth-bypass-test.md
- `authorized_comprehensive_security_assessment` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/authorized-comprehensive-security-assessment.md
- `authorized_controlled_validation` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/authorized-controlled-validation.md
- `authorized_credential_assessment` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/authorized-credential-assessment.md
- `authorized_environment_review` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/authorized-environment-review.md
- `authorized_injection_verification` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/authorized-injection-verification.md
- `authorized_network_exposure_assessment` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/authorized-network-exposure-assessment.md
- `authorized_template_validation` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/authorized-template-validation.md
- `authorized_web_application_assessment` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/authorized-web-application-assessment.md
- `auto_reverse_analyze` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/auto-reverse-analyze.md
- `bandit_scan` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/bandit-scan.md
- `bettercap_attack` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/bettercap-attack.md
- `browser_click` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/browser-click.md
- `browser_close_session` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/browser-close-session.md
- `browser_execute_js` — Execute — https://policylayer.com/tools/seac-25-kali-security-mcp/browser-execute-js.md
- …and 163 more: https://policylayer.com/tools/seac-25-kali-security-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=seac-25-kali-security-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/seac-25-kali-security-mcp