Web technology fingerprinting tool. Identifies CMS, frameworks, JavaScript libraries, and more.
AI agents call whatweb to retrieve information from MCP Kali Pentest without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
whatweb retrieves and analyzes publicly visible web server headers, metadata, and responses to classify technologies in use. This is purely informational reconnaissance with no side effects, no data modification, no command execution, and no destructive capability. It is a read-only information gathering tool typical of security enumeration workflows.
From the tool's definition whatweb is a 'Web technology fingerprinting tool' that 'Identifies CMS, frameworks, JavaScript libraries' — it performs passive reconnaissance and analysis without modifying systems or executing code.
Attacks that exploit this kind of access
Web technology fingerprinting tool. Identifies CMS, frameworks, JavaScript libraries, and more. It is categorised as a Read tool in the MCP Kali Pentest MCP Server, which means it retrieves data without modifying state.
Register the MCP Kali Pentest MCP server in PolicyLayer and add a rule for whatweb: 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 Pentest. Nothing to install.
whatweb is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the whatweb 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 whatweb. 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.
whatweb is provided by the MCP Kali Pentest MCP server (root1856/mcpkali). 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 →