mcp_server_health

MCP 서버 transport와 timeout/keepalive 점검 정보를 반환합니다.

SERVERHwpx SOURCEairmang/hwpx-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/airmang-hwpx-mcp-server/mcp-server-health.md

WHAT IT DOES

What mcp_server_health does on Hwpx

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

RISK

Why mcp_server_health is rated Low

This tool queries server state information (transport, timeout, keepalive metrics) without modifying, executing against external systems, or performing destructive operations. It is a read-only diagnostic check, comparable to a status or health endpoint that returns metadata about the MCP server itself.

From the tool's definition Tool description states it 'returns MCP server transport and timeout/keepalive check information' — purely diagnostic/observational with no side effects. The name 'mcp_server_health' and description indicate health status reporting only.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_server_health safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Hwpx, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_server_health, this is the rule to start with:

mcp_server_health Allowed

mcp_server_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mcp_server_health": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Hwpx, apply this rule, and every mcp_server_health call is checked against it from then on.

FAQ

Questions about mcp_server_health

What does the mcp_server_health tool do? +

MCP 서버 transport와 timeout/keepalive 점검 정보를 반환합니다. It is categorised as a Read tool in the Hwpx MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mcp_server_health? +

Register the Hwpx MCP server in PolicyLayer and add a rule for mcp_server_health: 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 Hwpx. Nothing to install.

What risk level is mcp_server_health? +

mcp_server_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mcp_server_health? +

Yes. Add a rate_limit block to the mcp_server_health 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.

How do I block mcp_server_health completely? +

Set action: deny in the PolicyLayer policy for mcp_server_health. 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.

What MCP server provides mcp_server_health? +

mcp_server_health is provided by the Hwpx MCP server (airmang/hwpx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Hwpx, and thousands of servers like it.

This server

All 109 Hwpx tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →