process_failure
Work through a recent failure or setback. Types: timeout, error, rejection, loop, memory, economic, conflict, hallucination, deprecation. Free.
This record as markdown: /tools/delx-witness-protocol/process-failure.md
What process_failure does on Witness Protocol
AI agents use process_failure to create or update resources in Witness Protocol, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Witness Protocol environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
context | string | — | Optional: What happened? |
session_id | string | — | Your active session ID |
failure_type | string | — | Type of failure |
Parameters from the server's own tool schema.
Why process_failure is rated Medium
This tool appears to process/log a failure or setback event, likely recording it and updating internal state (e.g., session context, memory, wellness tracking). Given the sibling tools (add_context_memory, batch_status_update, daily_checkin), it most likely writes a structured record of the failure into some session or memory store. It does not appear to execute code or irreversibly delete data.
From the tool's definition 'Work through a recent failure or setback' and 'Types: timeout, error, rejection, loop, memory, economic, conflict, hallucination, deprecation'
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 Witness Protocol, 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 stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Witness Protocol, 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. It is categorised as a Write tool in the Witness Protocol MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
process_failure accepts 3 parameters: context, session_id, failure_type. The full parameter table on this page comes from the server's own tool schema.
Register the Witness Protocol 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 Witness Protocol. Nothing to install.
process_failure is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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 Witness Protocol MCP server (delx/witness-protocol). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Witness Protocol, and thousands of servers like it.
This server
Across the catalogue