list_resumable_sessions
[SUPPORT] cdd0ef6c — Read-only: list this project's session recovery registry, newest heartbeat first, each with a freshly computed liveness classification (resumable/stale/dead/unknown). Dead rows are omitted by default.
This record as markdown: /tools/io-github-ajc3xc-meridian/list-resumable-sessions.md
What list_resumable_sessions does on Meridian
AI agents call list_resumable_sessions to retrieve information from Meridian without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
project_id | string | — | |
include_dead | boolean | — | |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
sprint_version | string | — |
Parameters from the server's own tool schema.
Why list_resumable_sessions is rated Low
Even though list_resumable_sessions only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_resumable_sessions 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 list_resumable_sessions, this is the rule to start with:
list_resumable_sessions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meridian, apply this rule, and every list_resumable_sessions call is checked against it from then on.
Questions about list_resumable_sessions
[SUPPORT] cdd0ef6c — Read-only: list this project's session recovery registry, newest heartbeat first, each with a freshly computed liveness classification (resumable/stale/dead/unknown). Dead rows are omitted by default. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
list_resumable_sessions accepts 5 parameters: limit, project_id, include_dead, project_name, sprint_version. The full parameter table on this page comes from the server's own tool schema.
Register the Meridian MCP server in PolicyLayer and add a rule for list_resumable_sessions: 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.
list_resumable_sessions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_resumable_sessions 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 list_resumable_sessions. 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.
list_resumable_sessions 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.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue