Skip to main content
Glama
Sign In
WAF MCP Server

WAF MCP Server

by KratosUAE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

waf_enable_rule

Re-enable a specific ModSecurity rule by its ID to restore security protection after troubleshooting false positives.

Instructions

Re-enable a previously disabled ModSecurity rule by ID.

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_enable_rule"
  }
}

Input Schema

NameRequiredDescriptionDefault
ruleIdYesModSecurity rule ID to re-enable (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?

No annotations are provided, and the description lacks behavioral details such as side effects (e.g., immediate activation), required permissions, or error conditions. The description minimally states the action without further 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 sentence with no unnecessary words. It is front-loaded and efficiently communicates the tool's purpose.

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 provides the core purpose. However, it omits context such as prerequisites (the rule must be disabled) and any consequences, making it adequate but not comprehensive.

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 covers the parameter fully (pattern, description), and the description adds an example ('e.g. 942140'). However, this adds little beyond what the schema already provides.

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 ('Re-enable') and the resource ('previously disabled ModSecurity rule by ID'). It is specific and distinguishes from sibling tools like waf_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 Guidelines3/5

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

The description implies usage when a rule needs to be re-enabled, but does not explicitly state when to use this tool versus alternatives (e.g., waf_disable_rule) or provide context on prerequisites or limitations.

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