waf_test · WAF MCP Server MCP: Risk & Policy

WHAT IT DOES

What waf_test does on WAF MCP Server

AI agents invoke waf_test 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.

WHY IT NEEDS A POLICY

Why waf_test needs a policy

The tool executes a test suite against the WAF (Web Application Firewall), triggering active test operations that probe blocking and pass-through rules. This is an Execute category action as it runs external operations.

From the tool's definition "Run the WAF test suite" - explicitly runs a test suite, which is an active execution of tests against the WAF system

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

waf_test Rate-limited

waf_test stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "waf_test": {
      "limits": [
        {
          "counter": "waf_test_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WAF MCP Server, so you can run agents against it safely.

FAQ

Questions about waf_test

What does the waf_test tool do? +

Run the WAF test suite to verify blocking and pass-through rules are working correctly. 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.

How do I enforce a policy on waf_test? +

Register the WAF MCP Server MCP server in PolicyLayer and add a rule for waf_test: 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.

What risk level is waf_test? +

waf_test is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit waf_test? +

Yes. Add a rate_limit block to the waf_test 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.

How do I block waf_test completely? +

Set action: deny in the PolicyLayer policy for waf_test. 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.

What MCP server provides waf_test? +

waf_test 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.