Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
WAF_MCP_HOSTNoBind address for network transports in MCP server127.0.0.1
WAF_MCP_PORTNoListen port for network transports in MCP server8000
WAF_RULES_FILENoPath to the regex rule JSON used by WAFEnginerules/waf_rules.mcp.json
WAF_MCP_TRANSPORTNoTransport mode for MCP server: stdio, http, or ssestdio

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
extensions
{
  "io.modelcontextprotocol/ui": {}
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
waf_check_requestB

对 HTTP 请求做 WAF 规则检测,返回命中的告警列表(无命中则为空列表)。url 建议包含完整查询串。

waf_rule_statsA

返回当前已加载规则的统计:含 rules_file、compiled_rules、compile_failed、compile_errors(截断)及分类计数。

waf_reload_rulesA

重新从磁盘加载 WAF_RULES_FILE(或默认 rules/waf_rules.mcp.json)并编译。用于修改规则文件后无需重启 MCP。

waf_run_self_testsA

运行内置 SQLi/XSS/命令注入/路径遍历样例,用于快速验证引擎是否检出攻击。

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: checking requests, reloading rules, viewing statistics, and running self-tests. No two tools overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent 'waf_verb_noun' pattern using snake_case, with clear and descriptive verbs (check, reload, rule_stats, run_self_tests).

Tool Count5/5

With 4 tools, the set is well-scoped for a WAF server, covering essential operations without being unnecessarily large or too minimal.

Completeness4/5

The tools cover the main use cases (request checking, rule management, statistics, testing). Minor gaps exist, such as no tool for individually viewing or modifying specific rules, but core workflows are supported.

Maintenance

ActivityInactive
ResponsivenessNo issues