Skip to main content
Glama
Sign In
WAF MCP Server

WAF MCP Server

by KratosUAE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

waf_disable_rule

Disable a ModSecurity rule by its ID to suppress false positives and allow legitimate traffic.

Instructions

Disable a specific ModSecurity rule by ID to suppress false positives.

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": {
      "ruleId": "<ruleId>"
    },
    "name": "waf_disable_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleIdYesModSecurity rule ID to disable (e.g. '942140')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A3.5/5.0
Behavior2/5

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

Annotations are absent, so description bears full responsibility. It discloses the action (disable) and purpose but omits critical details: whether the change is reversible (implied by sibling waf_enable_rule), immediate effect, side effects on other rules, or required permissions. A security-critical tool demands more transparency.

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

Conciseness5/5

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

The description is a single, efficient sentence with no redundant words. It front-loads the action and purpose without waste.

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?

For a simple tool with one parameter and no output schema, the description covers the basic action and purpose. However, it lacks usage guidance and behavioral details that would be expected for a tool that modifies security rules (e.g., impact, reversibility).

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 coverage is 100%, so the schema already provides pattern and example for ruleId. The description adds no additional meaning beyond the schema; it does not explain how to find the rule ID or its significance. Baseline 3 is appropriate.

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 verb 'Disable' and the resource 'ModSecurity rule by ID', and explains the purpose 'to suppress false positives.' It implicitly distinguishes from sibling tools like waf_enable_rule (enable) and waf_allow_ip (IP allowlisting).

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 purpose implies usage for false positive suppression but lacks explicit guidance on when to use vs alternatives (e.g., waf_fp_candidates, waf_enable_rule). No when-not-to-use or prerequisites are provided.

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