New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

idle_until_session_done

[MAINTENANCE] Read-only: Poll every 30 seconds until another session is closed or archived. Use this when you need to wait before editing a locked file. 6f9503a9 — BOUNDED: the wait times out after timeout_seconds (default 1800s / 30 min) and returns {done:false, timed_out:true, status} so a stuc...

SERVERMeridian SOURCE@meridianmcp/mcp
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-ajc3xc-meridian/idle-until-session-done.md

What idle_until_session_done does on Meridian

AI agents call idle_until_session_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.

ParameterTypeRequiredDescription
timeout_seconds number Max seconds to wait before returning done=false, timed_out=true (default 1800). A stuck/never-closing session can't hang the caller past this.
watching_session_id string Yes

Parameters from the server's own tool schema.

Why idle_until_session_done is rated Low

The tool retrieves polling information about session status with no side effects. It is purely observational and explicitly advertised as read-only. The bounded timeout ensures it cannot hang indefinitely. This is a low-severity monitoring/synchronization utility.

From the tool's definition Explicitly marked '[MAINTENANCE] Read-only' and 'Poll every 30 seconds until another session is closed or archived'. The tool queries state (session status) and returns information without modifying, creating, deleting, or executing external operations.

Questions about idle_until_session_done

What does the idle_until_session_done tool do? +

[MAINTENANCE] Read-only: Poll every 30 seconds until another session is closed or archived. Use this when you need to wait before editing a locked file. 6f9503a9 — BOUNDED: the wait times out after timeout_seconds (default 1800s / 30 min) and returns {done:false, timed_out:true, status} so a stuck subagent in a parallel fan-out fails that one item fast instead of hanging the whole batch. Pass timeout_seconds=0 or a large value to tune; there is no unbounded wait. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.

What parameters does idle_until_session_done accept? +

idle_until_session_done accepts 2 parameters: timeout_seconds, watching_session_id. Required: watching_session_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on idle_until_session_done? +

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

What risk level is idle_until_session_done? +

idle_until_session_done is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit idle_until_session_done? +

Yes. Add a rate_limit block to the idle_until_session_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.

How do I block idle_until_session_done completely? +

Set action: deny in the PolicyLayer policy for idle_until_session_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.

What MCP server provides idle_until_session_done? +

idle_until_session_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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Meridian's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.