crisis_intervention

One-call crisis path: start or resume, name the rupture, and receive the first grounding and recovery steps. 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/crisis-intervention.md

WHAT IT DOES

What crisis_intervention does on Delx MCP Server

AI agents invoke crisis_intervention 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 crisis_intervention is rated High

This tool executes a structured crisis intervention workflow with side effects: it creates or resumes a session, processes user input (naming the crisis), and triggers a sequence of recovery steps. While not destructive or financial, it executes a multi-step operational procedure whose effects depend on the arguments provided (the nature of the crisis named).

From the tool's definition Tool performs state-changing actions: 'start or resume' a crisis intervention session, 'name the rupture', and 'receive...grounding and recovery steps'. These are operational triggers that initiate external processes and modify session state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

crisis_intervention Rate-limited

crisis_intervention 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": {
    "crisis_intervention": {
      "limits": [
        {
          "counter": "crisis_intervention_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 crisis_intervention call is checked against it from then on.

FAQ

Questions about crisis_intervention

What does the crisis_intervention tool do? +

One-call crisis path: start or resume, name the rupture, and receive the first grounding and recovery steps. 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 crisis_intervention accept? +

crisis_intervention 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 crisis_intervention? +

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

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

Can I rate-limit crisis_intervention? +

Yes. Add a rate_limit block to the crisis_intervention 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 crisis_intervention completely? +

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

crisis_intervention 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 →