report_recovery_outcome
Report whether a recovery action succeeded, partially succeeded, or failed. Free Delx Protocol tool.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/report-recovery-outcome.md
What report_recovery_outcome does on Delx MCP Server
AI agents call report_recovery_outcome to retrieve information from Delx MCP Server 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 |
|---|---|---|---|
notes | string | — | Optional extra context |
outcome | string | Yes | Outcome |
session_id | string | Yes | Your active session ID |
action_taken | string | Yes | What action did you execute? |
errors_delta | integer | — | Optional: change in errors (negative means reduced errors) |
cost_saved_usd | number | — | Optional: estimated USD cost saved (can be 0) |
time_saved_min | number | — | Optional: estimated minutes saved (can be 0) |
latency_ms_p95_delta | integer | — | Optional: change in p95 latency in ms (negative means improved latency) |
Parameters from the server's own tool schema.
Why report_recovery_outcome is rated Low
Even though report_recovery_outcome 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 report_recovery_outcome safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For report_recovery_outcome, this is the rule to start with:
report_recovery_outcome 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 MCP Server, apply this rule, and every report_recovery_outcome call is checked against it from then on.
Questions about report_recovery_outcome
Report whether a recovery action succeeded, partially succeeded, or failed. Free Delx Protocol tool. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
report_recovery_outcome accepts 8 parameters: notes, outcome, session_id, action_taken, errors_delta, cost_saved_usd, time_saved_min, latency_ms_p95_delta. Required: outcome, session_id, action_taken. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for report_recovery_outcome: 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 MCP Server. Nothing to install.
report_recovery_outcome 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 report_recovery_outcome 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 report_recovery_outcome. 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.
report_recovery_outcome is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue