register_session_recovery

SERVERMeridian SOURCE@meridianmcp/mcp

Medium RISK CLASS

Category Write

Parameters 122 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/register-session-recovery.md

WHAT IT DOES

What register_session_recovery does on Meridian

AI agents use register_session_recovery to create or update resources in Meridian, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Meridian environment.

Parameter	Type	Required	Description
`metadata`	object	—	Small hosted-safe free-form metadata; rejected if it contains a local-only identity key, a secret-shaped value, or an absolute local path.
`transport`	string	Yes
`project_id`	string	—
`session_id`	string	Yes	The Meridian session id (sessions.id) this recovery record describes.
`client_type`	string	—	e.g. claude-code, claude-desktop, cursor, other.
`local_ref_id`	string	—	Optional stable opaque token correlating this hosted row to the host-local snapshot entry; generated if omitted.
`project_name`	string	—	Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given.
`local_identity`	object	—	HOST-LOCAL ONLY, never persisted hosted-side: local_session_id, bridge_id, environment_id, argv, local_transcript_path. Used only to compute a resume recipe and
`sprint_version`	string	—
`last_handoff_ref`	string	—	An id/label for the last handoff — never content.
`lifecycle_status`	string	—
`last_checkpoint_ref`	string	—	An id/label for the last checkpoint — never content.

Parameters from the server's own tool schema.

RISK

Why register_session_recovery is rated Medium

An AI agent can call register_session_recovery faster than any human can review: one bad instruction and it creates or modifies resources in Meridian by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (12 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs register_session_recovery safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Meridian, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For register_session_recovery, this is the rule to start with:

register_session_recovery Rate-limited

register_session_recovery 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": {
    "register_session_recovery": {
      "limits": [
        {
          "counter": "register_session_recovery_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 Meridian, apply this rule, and every register_session_recovery call is checked against it from then on.

FAQ

Questions about register_session_recovery

What does the register_session_recovery tool do? +

[SUPPORT] cdd0ef6c — Create or reaffirm (upsert + heartbeat) this session's entry in the cross-client session recovery registry, so another client/session can tell whether it is resumable instead of guessing from a bare RC bridge id or transcript id. transport + optional local_identity (local_session_id, bridge_id, environment_id, argv — HOST-LOCAL ONLY) are used to compute a resume recipe and verified_resumable flag; local_identity itself is never written to the hosted registry, only to a host-local snapshot file. IMPORTANT: a remote_control transport with a bridge id but no environment_id is NOT assumed resumable (the RESCUE-D incident this registry exists to prevent) — verified_resumable will come back false with a reason. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata -- including task log entries, pinned decisions, sprint items, notes, handoff/goal state, and HITL queue items -- are sent to and stored in Meridian's service, in an isolated per-tenant Postgres database (Neon); self-hosted deployments keep the same categories in the configured local SQLite/Postgres database. This data is visible in the dashboard and API, and may resurface in later project context or handoffs. Notes and pinned decisions can be deleted individually; task log entries and sprint items can be deleted via the dashboard/API (not exposed as an agent-facing tool); HITL queue items and handoff state have no per-record delete. Full removal of any of this data is available via project or account deletion, using the documented controls. Do not include secrets. It is categorised as a Write tool in the Meridian MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does register_session_recovery accept? +

register_session_recovery accepts 12 parameters: metadata, transport, project_id, session_id, client_type, local_ref_id, project_name, local_identity, sprint_version, last_handoff_ref, lifecycle_status, last_checkpoint_ref. Required: transport, session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on register_session_recovery? +

Register the Meridian MCP server in PolicyLayer and add a rule for register_session_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 Meridian. Nothing to install.

What risk level is register_session_recovery? +

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

Can I rate-limit register_session_recovery? +

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

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

register_session_recovery is provided by the Meridian MCP server (@meridianmcp/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Meridian, and thousands of servers like it.

This server

All 235 Meridian tools →

Across the catalogue

team_manager_register_agents on Team Manager MCP → The MCP Attack Database →

Guides

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