perform_health_check
Execute a health check immediately
This record as markdown: /tools/coder-rl-claude-mcpserver-dev1/perform-health-check.md
What perform_health_check does on Claude MCP Server Ecosystem
AI agents invoke perform_health_check to trigger actions in Claude MCP Server Ecosystem. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why perform_health_check is rated High
A health check actively probes services, endpoints, or infrastructure components to assess their status. This is an Execute-category action because it runs an external operation (querying services, pinging endpoints, etc.) rather than simply reading stored data. However, the blast radius is low since health checks are typically read-only probes with no side effects on data or system state.
From the tool's definition "Execute a health check immediately" — triggers an active operation against system components
Attacks that exploit this kind of access
The rule that runs perform_health_check safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude MCP Server Ecosystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For perform_health_check, this is the rule to start with:
perform_health_check stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude MCP Server Ecosystem, apply this rule, and every perform_health_check call is checked against it from then on.
Questions about perform_health_check
Execute a health check immediately. It is categorised as a Execute tool in the Claude MCP Server Ecosystem MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Claude MCP Server Ecosystem MCP server in PolicyLayer and add a rule for perform_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 Claude MCP Server Ecosystem. Nothing to install.
perform_health_check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the perform_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 perform_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.
perform_health_check is provided by the Claude MCP Server Ecosystem MCP server (coder-rl/claude_mcpserver_dev1). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude MCP Server Ecosystem, and thousands of servers like it.
Across the catalogue