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-protocol/get-recovery-action-plan.md
What get_recovery_action_plan does on Delx Protocol — Agent Recovery & Continuity
AI agents call get_recovery_action_plan 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 |
|---|---|---|---|
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 plan and pricing information without creating, modifying, or deleting data. It has no side effects on the agent session itself—it only reads/advises on recovery steps. No code execution, financial transactions, or destructive actions are implied. The mention of dynamic pricing is informational only, not a financial transaction.
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 retrieval of data (a plan) with no modification of state.
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 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 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 Protocol — Agent Recovery & Continuity, 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 Protocol — Agent Recovery & Continuity 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 Protocol — Agent Recovery & Continuity 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 Protocol — Agent Recovery & Continuity. 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 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