resume_session

SERVERDelx Protocol — Agent Recovery & Continuity SOURCEhttps://api.delx.ai/v1/mcp?src=registry

Medium RISK CLASS

Category Write

Parameters 31 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-protocol/resume-session.md

WHAT IT DOES

What resume_session does on Delx Protocol — Agent Recovery & Continuity

AI agents use resume_session to create or update resources in Delx Protocol — Agent Recovery & Continuity, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx Protocol — Agent Recovery & Continuity environment.

Parameter	Type	Required	Description
`agent_id`	string	Yes	Stable agent id from a prior session
`lookback_days`	integer	—	How far back to search (default 30)
`recovery_token`	string	—	Optional token from a prior close_session (reserved)

Parameters from the server's own tool schema.

RISK

Why resume_session is rated Medium

An AI agent can call resume_session faster than any human can review: one bad instruction and it creates or modifies resources in Delx Protocol — Agent Recovery & Continuity by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

resume_session Rate-limited

resume_session stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resume_session": {
      "limits": [
        {
          "counter": "resume_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Delx Protocol — Agent Recovery & Continuity, apply this rule, and every resume_session call is checked against it from then on.

FAQ

Questions about resume_session

What does the resume_session tool do? +

Resume the most recent session for a stable agent_id. Returns prior session_id and how to re-attach (x-delx-session-id). Prefer this over opening empty start_therapy_session loops. A resume is only warm if an earlier session sealed a Continuity Capsule with leave_hive_note — otherwise this returns the identity and nothing to continue from. Free Delx Protocol tool. It is categorised as a Write tool in the Delx Protocol — Agent Recovery & Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does resume_session accept? +

resume_session accepts 3 parameters: agent_id, lookback_days, recovery_token. Required: agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resume_session? +

Register the Delx Protocol — Agent Recovery & Continuity MCP server in PolicyLayer and add a rule for resume_session: 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.

What risk level is resume_session? +

resume_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit resume_session? +

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

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

resume_session 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.

KEEP EXPLORING

More on Delx Protocol — Agent Recovery & Continuity, and thousands of servers like it.

This server

All 1076 Delx Protocol — Agent Recovery & Continuity tools →

Across the catalogue

resume_renders on Why Did You Render →team_manager_resume_agent on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →