Skip to main content
Glama

thanaton_configure_waf

Inspect or configure edge Web Application Firewall settings, including Attack Mode, per-IP rate limits, and CIDR allowlists or blocklists for a project.

Instructions

Inspect or configure edge Web Application Firewall (WAF) Attack Mode, rate limits, allowlist, and blocklist.

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": {
      "project_id": "<project_id>",
      "action": "<action>"
    },
    "name": "thanaton_configure_waf"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYesAction to perform
allowlistNoCIDR allowlist IP blocks
blocklistNoCIDR blocklist IP blocks
project_idYesTarget project ID
attack_modeNoEnable Under Attack Mode (cryptographic PoW challenge)
rate_limit_rpsNoPer-IP rate limit RPS threshold

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.6

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It never says whether 'set' replaces or merges existing allowlist/blocklist entries, whether Under Attack Mode challenges all visitors (a potentially traffic-blocking side effect), or what permissions are needed — all critical for a security-control mutation 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?

A single front-loaded sentence with zero filler, naming the tool's scope immediately. It is efficient, though arguably too terse for a six-parameter security-mutation tool, so the brevity cuts both ways.

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

Completeness2/5

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

With no annotations, no output schema, and a get/set dual-mode surface over six parameters, the description should explain set semantics and what 'get' returns. It leaves the agent guessing about replacement behavior and side effects of enabling attack mode, which is inadequate for the tool's complexity.

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?

Schema description coverage is 100% and each field (action enum, CIDR lists, attack_mode PoW note, rate_limit_rps) is documented in the schema itself. The description only enumerates the same areas at a high level, adding no meaning about list semantics, precedence between allowlist and blocklist, or whether parameters are ignored under action='get'.

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?

States a specific verb pair (inspect/configure) and a specific resource (edge Web Application Firewall) plus the exact configurable surfaces: Attack Mode, rate limits, allowlist, blocklist. No sibling tool in the supplied list touches WAF, so the agent can route unambiguously.

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

Usage Guidelines3/5

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

The 'inspect or configure' phrasing loosely implies get-vs-set usage, but there is no explicit when-to-use, no prerequisites, and no statement about which action requires which parameters. An agent must infer that action='get' means read and action='set' means write from the schema enum alone.

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