node_health
Score the health of every node Denpex is monitoring in your fleet, worst first. Use it to answer 'which nodes should I exclude from this job?' before scheduling, or 'what else is degrading?' after an incident. Scale+ feature; requires the Denpex agent to be reporting.
This record as markdown: /tools/denpex-mcp/node-health.md
What node_health does on Denpex
AI agents invoke node_health to trigger actions in Denpex. 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 node_health is rated High
node_health triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs node_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denpex, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For node_health, this is the rule to start with:
node_health 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 Denpex, apply this rule, and every node_health call is checked against it from then on.
Questions about node_health
Score the health of every node Denpex is monitoring in your fleet, worst first. Use it to answer 'which nodes should I exclude from this job?' before scheduling, or 'what else is degrading?' after an incident. Scale+ feature; requires the Denpex agent to be reporting. It is categorised as a Execute tool in the Denpex MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Denpex MCP server in PolicyLayer and add a rule for node_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 Denpex. Nothing to install.
node_health 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 node_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.
Set action: deny in the PolicyLayer policy for node_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.
node_health is provided by the Denpex MCP server (denpex-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denpex, and thousands of servers like it.
Across the catalogue