Run WordPress vulnerability scanner on whitelisted targets.
AI agents invoke wpscan_check to trigger actions in Kali Pentest 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.
WPScan is an active scanning tool that sends requests to the target to enumerate WordPress users, plugins, themes, and known vulnerabilities. This is an Execute-category action because it triggers external operations (network requests, active probing) against a target system.
From the tool's definition 'Run WordPress vulnerability scanner' — actively executes WPScan against a target, performing active probing and enumeration of WordPress installations, plugins, themes, and known CVEs
Attacks that exploit this kind of access
Run WordPress vulnerability scanner on whitelisted targets. It is categorised as a Execute tool in the Kali Pentest MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali Pentest MCP Server MCP server in PolicyLayer and add a rule for wpscan_check: 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 Kali Pentest MCP Server. Nothing to install.
wpscan_check 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_check 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_check. 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_check is provided by the Kali Pentest MCP Server MCP server (salmanfaris7/kali-penetrationtest-mcp-server). 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 →