Web technology fingerprinting
AI agents call whatweb to retrieve information from PenTest MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Web technology fingerprinting is a reconnaissance activity that queries and analyzes web server responses to identify software versions and technologies in use. It does not execute code, modify data, delete resources, or trigger external operations with side effects. While it gathers information useful for security assessments, it performs read-only operations that produce no lasting changes to target systems.
From the tool's definition Tool name 'whatweb' and description 'Web technology fingerprinting' indicate passive reconnaissance that identifies technologies running on web targets without modifying or executing operations on those targets.
Attacks that exploit this kind of access
Web technology fingerprinting. It is categorised as a Read tool in the PenTest MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PenTest MCP Server 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 PenTest MCP Server. 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 PenTest MCP Server MCP server (mohitsahoo/mcptoolforwebvulnerabilities-). 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 →