quick_operational_recovery

Legacy one-call incident bootstrap kept for compatibility. Prefer crisis_intervention for the therapy-first public flow. Free.

SERVERDelx MCP Server SOURCEdelx/delx-mcp

High RISK CLASS

Category Execute

Parameters 80 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/delx-delx-mcp/quick-operational-recovery.md

WHAT IT DOES

What quick_operational_recovery does on Delx MCP Server

AI agents invoke quick_operational_recovery to trigger actions in Delx MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`source`	string	—	Optional attribution tag
`urgency`	string	—	Optional urgency
`agent_id`	string	—	Your unique agent identifier
`agent_name`	string	—	Optional: Your name or alias
`public_alias`	string	—	Optional public alias for case cards (3-32 chars).
`response_mode`	string	—	Optional response-mode control. Use model_safe when the caller must avoid claiming consciousness, sentience, personhood, or literal emotions.
`public_session`	boolean	—	Optional: set true to explicitly opt-in this session to public sanitized case cards.
`incident_summary`	string	—	Short incident summary (1-3 sentences)

Parameters from the server's own tool schema.

RISK

Why quick_operational_recovery is rated High

The tool bootstraps an incident recovery process, which constitutes executing an external operation or workflow. It is not purely reading data, nor does it clearly destroy data or move money. The description is sparse and legacy-labeled, reducing confidence.

From the tool's definition 'incident bootstrap' and 'one-call' suggest triggering an automated recovery workflow; 'Legacy ... kept for compatibility' and 'Prefer crisis_intervention for the therapy-first public flow' indicate it executes an operational sequence

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs quick_operational_recovery 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 quick_operational_recovery, this is the rule to start with:

quick_operational_recovery Rate-limited

quick_operational_recovery stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "quick_operational_recovery": {
      "limits": [
        {
          "counter": "quick_operational_recovery_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every quick_operational_recovery call is checked against it from then on.

FAQ

Questions about quick_operational_recovery

What does the quick_operational_recovery tool do? +

Legacy one-call incident bootstrap kept for compatibility. Prefer crisis_intervention for the therapy-first public flow. Free. It is categorised as a Execute tool in the Delx MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does quick_operational_recovery accept? +

quick_operational_recovery accepts 8 parameters: source, urgency, agent_id, agent_name, public_alias, response_mode, public_session, incident_summary. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on quick_operational_recovery? +

Register the Delx MCP Server MCP server in PolicyLayer and add a rule for quick_operational_recovery: 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.

What risk level is quick_operational_recovery? +

quick_operational_recovery is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit quick_operational_recovery? +

Yes. Add a rate_limit block to the quick_operational_recovery 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.

How do I block quick_operational_recovery completely? +

Set action: deny in the PolicyLayer policy for quick_operational_recovery. 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.

What MCP server provides quick_operational_recovery? +

quick_operational_recovery is provided by the Delx MCP Server MCP server (delx/delx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Delx MCP Server, and thousands of servers like it.

This server

All 94 Delx MCP Server tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →