Change WAF engine mode: On (actively blocking), Off (disabled), or DetectionOnly (log without blocking).
AI agents invoke waf_set_engine to trigger actions in WAF MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool changes the operational mode of a Web Application Firewall. Setting it to 'Off' disables all WAF protections entirely, exposing the application to attacks. This is an external system configuration change with major security implications — disabling a WAF is not destructive in the data-deletion sense, but it triggers a critical operational change.
From the tool's definition Change WAF engine mode: On (actively blocking), Off (disabled), or DetectionOnly (log without blocking)
Attacks that exploit this kind of access
Change WAF engine mode: On (actively blocking), Off (disabled), or DetectionOnly (log without blocking). It is categorised as a Execute tool in the WAF MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WAF MCP Server MCP server in PolicyLayer and add a rule for waf_set_engine: 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_set_engine is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the waf_set_engine 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_set_engine. 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_set_engine 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 →