get_session_recovery
[SUPPORT] cdd0ef6c — Read-only: fetch one session's recovery record (by session_id or recovery_id) plus, by default, a continuation payload that RE-DERIVES the live sprint board and this session's own still-active file claims — never a stored /goal body. resume_recipe is resolved from THIS machin...
This record as markdown: /tools/io-github-ajc3xc-meridian/get-session-recovery.md
What get_session_recovery does on Meridian
AI agents call get_session_recovery 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 |
|---|---|---|---|
project_id | string | — | |
session_id | string | — | |
recovery_id | string | — | |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
include_continuation | boolean | — |
Parameters from the server's own tool schema.
Why get_session_recovery is rated Low
Even though get_session_recovery 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 get_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 get_session_recovery, this is the rule to start with:
get_session_recovery 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 get_session_recovery call is checked against it from then on.
Questions about get_session_recovery
[SUPPORT] cdd0ef6c — Read-only: fetch one session's recovery record (by session_id or recovery_id) plus, by default, a continuation payload that RE-DERIVES the live sprint board and this session's own still-active file claims — never a stored /goal body. resume_recipe is resolved from THIS machine's own host-local snapshot only and is null when this machine never registered that session's local identity. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
get_session_recovery accepts 5 parameters: project_id, session_id, recovery_id, project_name, include_continuation. 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 get_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.
get_session_recovery 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 get_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.
Set action: deny in the PolicyLayer policy for get_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.
get_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.
More on Meridian, and thousands of servers like it.
This server
Across the catalogue