New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

wpscan_analyze

Execute WPScan for WordPress vulnerability scanning with enhanced logging.

SERVERIntellirecon Console SOURCEdokotela021/intellirecon-console
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/intellirecon-console/wpscan-analyze.md

What wpscan_analyze does on Intellirecon Console

AI agents invoke wpscan_analyze to trigger actions in Intellirecon Console. 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 wpscan_analyze is rated High

This tool executes WPScan, an external security scanning tool, against WordPress targets. It triggers active reconnaissance and vulnerability scanning operations against external systems, which constitutes executing an external tool with real-world side effects. Misuse by an AI agent could result in unauthorized scanning of targets, potential legal liability, and triggering security alerts on victim systems.

From the tool's definition Execute WPScan for WordPress vulnerability scanning with enhanced logging

Questions about wpscan_analyze

What does the wpscan_analyze tool do? +

Execute WPScan for WordPress vulnerability scanning with enhanced logging. It is categorised as a Execute tool in the Intellirecon Console 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_analyze? +

Register the Intellirecon Console 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 Intellirecon Console. Nothing to install.

What risk level is wpscan_analyze? +

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

Can I rate-limit wpscan_analyze? +

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.

How do I block wpscan_analyze completely? +

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.

What MCP server provides wpscan_analyze? +

wpscan_analyze is provided by the Intellirecon Console MCP server (dokotela021/intellirecon-console). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Intellirecon Console, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Intellirecon Console's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.