Drill into events that triggered a specific rule. Shows timestamps, IPs, methods, URIs, HTTP codes, and matched data.
AI agents call waf_events_by_rule 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.
This tool retrieves and queries existing WAF event logs filtered by rule ID. It performs analysis and drill-down operations on historical security event data without creating, modifying, deleting, or executing any operations.
From the tool's definition Tool description states 'Drill into events that triggered a specific rule. Shows timestamps, IPs, methods, URIs, HTTP codes, and matched data.' The verb 'Shows' and the listing of query outputs (timestamps, IPs, methods, URIs, HTTP codes, matched data)…
Attacks that exploit this kind of access
Drill into events that triggered a specific rule. Shows timestamps, IPs, methods, URIs, HTTP codes, and matched data. 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_events_by_rule: 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_events_by_rule 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_events_by_rule 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_events_by_rule. 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_events_by_rule 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 →