stateset_health_check
Checks overall server health and connectivity. Returns: API connection status, rate limiter state, circuit breaker state (open/closed/half-open), memory usage, and server info. Use to diagnose issues when operations are failing.
This record as markdown: /tools/stateset-mcp-server/stateset-health-check.md
What stateset_health_check does on Stateset
AI agents call stateset_health_check to retrieve information from Stateset without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stateset_health_check is rated Low
This tool only retrieves and reports status information about the server. It does not modify, delete, execute commands, or create any changes to data or system state. The explicit purpose is diagnosis and monitoring, making it a pure Read operation. The low severity reflects that misuse would only retrieve non-sensitive diagnostic metadata.
From the tool's definition Tool description states it "Checks overall server health and connectivity" and "Returns: API connection status, rate limiter state, circuit breaker state, memory usage, and server info." These are all read-only diagnostic operations with no side effects.
Attacks that exploit this kind of access
The rule that runs stateset_health_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Stateset, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stateset_health_check, this is the rule to start with:
stateset_health_check 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 Stateset, apply this rule, and every stateset_health_check call is checked against it from then on.
Questions about stateset_health_check
Checks overall server health and connectivity. Returns: API connection status, rate limiter state, circuit breaker state (open/closed/half-open), memory usage, and server info. Use to diagnose issues when operations are failing. It is categorised as a Read tool in the Stateset MCP Server, which means it retrieves data without modifying state.
Register the Stateset MCP server in PolicyLayer and add a rule for stateset_health_check: 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 Stateset. Nothing to install.
stateset_health_check 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 stateset_health_check 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 stateset_health_check. 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.
stateset_health_check is provided by the Stateset MCP server (stateset/stateset-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Stateset, and thousands of servers like it.
This server
Across the catalogue