get_recovery_action_plan
Step-by-step recovery plan for a failing, drifting, or looping agent session. Pricing is dynamic; check /api/v1/tools.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/get-recovery-action-plan.md
What get_recovery_action_plan does on Delx MCP Server
AI agents call get_recovery_action_plan 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 |
|---|---|---|---|
urgency | string | — | Optional urgency |
session_id | string | Yes | Your active session ID |
incident_summary | string | Yes | What incident are you trying to recover from? |
Parameters from the server's own tool schema.
Why get_recovery_action_plan is rated Low
This tool retrieves or queries a recovery action plan—diagnostic information about an agent session state. It has no side effects on data or system state; it does not execute commands, modify data, delete resources, or commit financial obligations. The mention of 'dynamic pricing' and an API endpoint is informational only, not an actual financial transaction by this tool itself.
From the tool's definition Tool name 'get_recovery_action_plan' and description 'Step-by-step recovery plan for a failing, drifting, or looping agent session' indicate data retrieval with no modification.
Attacks that exploit this kind of access
The rule that runs get_recovery_action_plan 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 get_recovery_action_plan, this is the rule to start with:
get_recovery_action_plan 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 get_recovery_action_plan call is checked against it from then on.
Questions about get_recovery_action_plan
Step-by-step recovery plan for a failing, drifting, or looping agent session. Pricing is dynamic; check /api/v1/tools. It is categorised as a Read tool in the Delx MCP Server MCP Server, which means it retrieves data without modifying state.
get_recovery_action_plan accepts 3 parameters: urgency, session_id, incident_summary. Required: session_id, incident_summary. 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 get_recovery_action_plan: 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.
get_recovery_action_plan 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 get_recovery_action_plan 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 get_recovery_action_plan. 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.
get_recovery_action_plan 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