process_failure
Work through a recent failure or setback. Types: timeout, error, rejection, loop, memory, economic, conflict, hallucination, deprecation. Free Delx Protocol tool.
This record as markdown: /tools/io-github-davidmosiah-delx-protocol/process-failure.md
What process_failure does on Delx Protocol — Agent Recovery & Continuity
AI agents call process_failure to retrieve information from Delx Protocol — Agent Recovery & Continuity without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
context | string | — | Optional: What happened? |
session_id | string | Yes | Your active session ID |
failure_type | string | Yes | Type of failure |
Parameters from the server's own tool schema.
Why process_failure is rated Low
Even though process_failure only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs process_failure safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Protocol — Agent Recovery & Continuity, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For process_failure, this is the rule to start with:
process_failure 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 Delx Protocol — Agent Recovery & Continuity, apply this rule, and every process_failure call is checked against it from then on.
Questions about process_failure
Work through a recent failure or setback. Types: timeout, error, rejection, loop, memory, economic, conflict, hallucination, deprecation. Free Delx Protocol tool. It is categorised as a Read tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it retrieves data without modifying state.
process_failure accepts 3 parameters: context, session_id, failure_type. Required: session_id, failure_type. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for process_failure: 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 Delx Protocol — Agent Recovery & Continuity. Nothing to install.
process_failure 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 process_failure 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 process_failure. 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.
process_failure is provided by the Delx Protocol — Agent Recovery & Continuity MCP server (https://api.delx.ai/v1/mcp?src=registry). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.
Across the catalogue