waf_check_request
对 HTTP 请求做 WAF 规则检测,返回命中的告警列表(无命中则为空列表)。url 建议包含完整查询串。
This record as markdown: /tools/12211725-star-hospital-waf-mcp/waf-check-request.md
What waf_check_request does on Hospital WAF MCP
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.
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 definition Tool description indicates it 'checks HTTP requests against WAF rules and returns a list of triggered alerts (empty list if no matches)'.
Attacks that exploit this kind of access
The rule that runs waf_check_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hospital WAF MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For waf_check_request, this is the rule to start with:
waf_check_request is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Hospital WAF MCP, apply this rule, and every waf_check_request call is checked against it from then on.
Questions about waf_check_request
对 HTTP 请求做 WAF 规则检测,返回命中的告警列表(无命中则为空列表)。url 建议包含完整查询串。. It is categorised as a Read tool in the Hospital WAF MCP MCP Server, which means it retrieves data without modifying state.
Register the Hospital WAF MCP server in PolicyLayer and add a rule for waf_check_request: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Hospital WAF MCP. Nothing to install.
waf_check_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the waf_check_request rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for waf_check_request. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
waf_check_request is provided by the Hospital WAF MCP server (12211725-star/hospital-waf-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hospital WAF, and thousands of servers like it.
This server
Across the catalogue