Full deep-dive into a single event by index. Shows all request headers, body snippet, all rule matches with matched data, and response code.
AI agents call waf_event_detail to retrieve information from WAF MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves and displays detailed diagnostic information about a WAF event without modifying state, executing commands, or deleting data. This is a read-only query operation with no side effects. Severity is low because the tool only reveals historical event metadata that would already be available to authorized users monitoring the WAF system.
From the tool's definition Tool description states it 'Shows all request headers, body snippet, all rule matches with matched data, and response code' — purely informational retrieval of event details with no modification, execution, or deletion of data.
Attacks that exploit this kind of access
Full deep-dive into a single event by index. Shows all request headers, body snippet, all rule matches with matched data, and response code. It is categorised as a Read tool in the WAF MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WAF MCP Server MCP server in PolicyLayer and add a rule for waf_event_detail: 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 WAF MCP Server. Nothing to install.
waf_event_detail 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 waf_event_detail 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 waf_event_detail. 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.
waf_event_detail is provided by the WAF MCP Server MCP server (kratosuae/waf_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 →