predict_failures
List the predictive risk scores Denpex has computed for your fleet — nodes whose counters are trending toward a failure that has not happened yet (rising correctable ECC, row-remap pressure, PCIe replays, thermal drift). Use it to drain a node on your schedule instead of the cluster's. Scale+ fea...
This record as markdown: /tools/denpex-mcp/predict-failures.md
What predict_failures does on Denpex
AI agents invoke predict_failures 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 predict_failures is rated High
predict_failures 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.
Attacks that exploit this kind of access
The rule that runs predict_failures 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 predict_failures, this is the rule to start with:
predict_failures 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 predict_failures call is checked against it from then on.
Questions about predict_failures
List the predictive risk scores Denpex has computed for your fleet — nodes whose counters are trending toward a failure that has not happened yet (rising correctable ECC, row-remap pressure, PCIe replays, thermal drift). Use it to drain a node on your schedule instead of the cluster's. Scale+ feature. 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 predict_failures: 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.
predict_failures 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 predict_failures 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 predict_failures. 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.
predict_failures 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