AI agents call wafw00f_detect to retrieve information from Redteam without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
wafw00f is a reconnaissance/detection tool that passively or actively probes a target to identify what WAF, if any, is in front of it. It reads/queries network responses but does not modify data, execute payloads, or cause destruction.
From the tool's definition Detect Web Application Firewalls (WAF) protecting a target
Attacks that exploit this kind of access
Detect Web Application Firewalls (WAF) protecting a target. It is categorised as a Read tool in the Redteam MCP Server, which means it retrieves data without modifying state.
Register the Redteam MCP server in PolicyLayer and add a rule for wafw00f_detect: 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 Redteam. Nothing to install.
wafw00f_detect 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 wafw00f_detect 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 wafw00f_detect. 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.
wafw00f_detect is provided by the Redteam MCP server (samirjani03/redteam-mcp). 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 →