Skip to main content
Glama
Sign In
WAF MCP Server

WAF MCP Server

by KratosUAE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

waf_allow_ip

Whitelist an IP address to bypass WAF inspection, allowing trusted traffic to skip OWASP ModSecurity CRS rules.

Instructions

Whitelist an IP address to bypass WAF inspection entirely.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ip": "<ip>"
    },
    "name": "waf_allow_ip"
  }
}

Input Schema

NameRequiredDescriptionDefault
ipYesIP address to whitelist (bypass WAF inspection)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description discloses the key behavioral trait ('bypass WAF inspection entirely'), but since no annotations are provided, it carries the full burden. It does not detail reversibility, scope, or limitations, which are important for a security tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, concise sentence that is front-loaded with the main action. It is not verbose, but it could be slightly more informative without losing conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (one parameter, no output schema), the description is adequate but lacks details on prerequisites, side effects, or security implications. It serves as a minimal viable description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already provides a description for the 'ip' parameter, and the tool description does not add new semantic information beyond what is in the schema. With 100% schema coverage, the baseline is 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Whitelist an IP address') and the effect ('to bypass WAF inspection entirely'), distinguishing it from sibling tools like waf_deny_ip (block) and waf_disable_rule (disable rule).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage when you want to bypass WAF for an IP, but it provides no explicit guidance on when not to use it or when to prefer alternatives like waf_deny_ip. No context about prerequisites or side effects is given.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools