AI agents invoke droopescan_scan to trigger actions in Kali. 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.
droopescan is a web CMS scanner (targeting Drupal, WordPress, etc.) used to identify vulnerabilities in target systems. The tool executes an external security scanning tool against potentially remote targets. This is an Execute category action — it runs an external program whose effects depend on the arguments provided (target URL/host).
From the tool's definition 'Execute droopescan with the provided parameters' on a server described as providing 'penetration testing and security assessment tool interfaces' supporting 'network scanning, web scanning, password attacks'
Attacks that exploit this kind of access
Execute droopescan with the provided parameters. It is categorised as a Execute tool in the Kali MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kali MCP server in PolicyLayer and add a rule for droopescan_scan: 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. Nothing to install.
droopescan_scan 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 droopescan_scan 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 droopescan_scan. 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.
droopescan_scan is provided by the Kali MCP server (pentestt00ls/kali-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 →