AI agents invoke cewl_generate 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.
CeWL (Custom Word List generator) crawls a target URL and generates wordlists used in password cracking/brute-force attacks. This constitutes an active external operation (web spidering of a target) and produces artifacts used for offensive security purposes. The description is empty, lowering confidence slightly, but the tool name and server context strongly imply this function.
From the tool's definition Tool name 'cewl_generate' on a Kali Linux penetration testing MCP server supporting 'password attacks' among 90+ tools. CeWL is a well-known Kali Linux tool that spiders a target website to generate custom wordlists for password attacks.
Attacks that exploit this kind of access
cewl_generate. 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 cewl_generate: 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.
cewl_generate 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 cewl_generate 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 cewl_generate. 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.
cewl_generate 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 →