idle_until_all_done
[MAINTENANCE] PARALLEL COORDINATION (d3a3a01d): non-blocking barrier check across sibling sessions. Returns {all_done, pending, statuses}; a session is done when closed/archived/missing. The server can't block, so poll until all_done is true — the A2A 'wait for X, Y, Z to finish' primitive. Persi...
This record as markdown: /tools/io-github-ajc3xc-meridian/idle-until-all-done.md
What idle_until_all_done does on Meridian
AI agents call idle_until_all_done 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 |
|---|---|---|---|
session_ids | array | Yes | Sessions to wait on. |
Parameters from the server's own tool schema.
Why idle_until_all_done is rated Low
The tool performs a status poll/check across sibling sessions and returns state information without modifying or deleting any data. It is a read-only coordination primitive (a barrier check). The note about persistent-state disclosure refers to data already stored, not new writes caused by this tool.
From the tool's definition non-blocking barrier check across sibling sessions. Returns {all_done, pending, statuses}; a session is done when closed/archived/missing
Attacks that exploit this kind of access
The rule that runs idle_until_all_done 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 idle_until_all_done, this is the rule to start with:
idle_until_all_done 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 idle_until_all_done call is checked against it from then on.
Questions about idle_until_all_done
[MAINTENANCE] PARALLEL COORDINATION (d3a3a01d): non-blocking barrier check across sibling sessions. Returns {all_done, pending, statuses}; a session is done when closed/archived/missing. The server can't block, so poll until all_done is true — the A2A 'wait for X, Y, Z to finish' primitive. Persistent-state disclosure: on hosted Meridian, supplied text and project/session metadata are sent to and stored in Meridian's service; self-hosted deployments keep them in the configured local SQLite/Postgres database. This data is visible in the dashboard/API and later project context or handoffs. Delete individual tasks, notes, or decisions where supported, or delete the project/account using the documented controls. Do not include secrets. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
idle_until_all_done accepts 1 parameter: session_ids. Required: session_ids. 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 idle_until_all_done: 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.
idle_until_all_done 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 idle_until_all_done 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 idle_until_all_done. 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.
idle_until_all_done 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