Execute WPScan WordPress vulnerability scanner.
AI agents invoke wpscan_analyze to trigger actions in MCP Kali 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.
This tool runs WPScan, an active vulnerability scanner that probes WordPress installations for security weaknesses. It executes external scanning operations against target systems, which can be intrusive and potentially trigger security alerts or cause unintended side effects on target systems. Running unauthorized scans against systems can be illegal.
From the tool's definition Execute WPScan WordPress vulnerability scanner
Attacks that exploit this kind of access
Execute WPScan WordPress vulnerability scanner. It is categorised as a Execute tool in the MCP Kali Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Kali Server MCP server in PolicyLayer and add a rule for wpscan_analyze: 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 Server. Nothing to install.
wpscan_analyze 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_analyze 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_analyze. 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_analyze is provided by the MCP Kali Server MCP server (wh0am123/mcp-kali-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.