WordPress vulnerability scanner. Detects vulnerable plugins, themes, and WordPress core issues.
AI agents invoke wpscan to trigger actions in MCP Kali Pentest. 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.
WPScan actively probes and scans WordPress installations to enumerate users, detect vulnerable plugins/themes, and identify core vulnerabilities. This constitutes active external operations against target systems — not merely reading local data. In the context of a penetration testing framework with exploitation tools as siblings, misuse could facilitate unauthorized access to WordPress sites.
From the tool's definition WordPress vulnerability scanner. Detects vulnerable plugins, themes, and WordPress core issues.
Attacks that exploit this kind of access
WordPress vulnerability scanner. Detects vulnerable plugins, themes, and WordPress core issues. It is categorised as a Execute tool in the MCP Kali Pentest MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for wpscan: 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 MCP Kali Pentest. Nothing to install.
wpscan is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the wpscan 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.
Set action: deny in the PolicyLayer policy for wpscan. 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.
wpscan is provided by the MCP Kali Pentest MCP server (root1856/mcpkali). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →