resume_session
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 return...
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/resume-session.md
What resume_session does on Delx MCP Server
AI agents use resume_session to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server 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.
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 MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs resume_session 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 resume_session, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx MCP Server, apply this rule, and every resume_session call is checked against it from then on.
Questions about resume_session
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 MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
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.
Register the Delx MCP Server 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 MCP Server. Nothing to install.
resume_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
resume_session 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