# waf_check_request

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

Agent View of the PolicyLayer registry record for `waf_check_request`. HTML page: https://policylayer.com/tools/12211725-star-hospital-waf-mcp/waf-check-request

## Facts

- Tool: `waf_check_request`
- Server: Hospital WAF MCP (`12211725-star/hospital-waf-mcp`) — https://policylayer.com/tools/12211725-star-hospital-waf-mcp.md
- Homepage: https://github.com/12211725-star/hospital-waf-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "waf_check_request",
    "arguments": {}
  }
}
```

## Why waf_check_request is rated Low

waf_check_request performs query/analysis on an HTTP request to determine if it matches security rules. No data is created, modified, deleted, or irreversibly altered. No code execution or financial transactions occur. The tool is read-only introspection of request compliance, placing it firmly in the Read category with low severity risk.

From the tool's own definition: "Tool description indicates it 'checks HTTP requests against WAF rules and returns a list of triggered alerts (empty list if no matches)'."

## Use case

AI agents call waf_check_request to retrieve information from Hospital WAF MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Hospital WAF MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "waf_check_request": {}
  }
}
```

## Other tools on Hospital WAF MCP (3)

- `waf_run_self_tests` — Execute — https://policylayer.com/tools/12211725-star-hospital-waf-mcp/waf-run-self-tests.md
- `waf_reload_rules` — Read — https://policylayer.com/tools/12211725-star-hospital-waf-mcp/waf-reload-rules.md
- `waf_rule_stats` — Read — https://policylayer.com/tools/12211725-star-hospital-waf-mcp/waf-rule-stats.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=12211725-star-hospital-waf-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/12211725-star-hospital-waf-mcp