list_sessions
[MAINTENANCE] Read-only: List active sessions for a project. Useful for planning chat to see what's currently running before filing new sprint items.
This record as markdown: /tools/io-github-ajc3xc-meridian/list-sessions.md
What list_sessions does on Meridian
AI agents call list_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 |
|---|---|---|---|
status | string | — | Filter by status: 'active' (default), or 'all' for all sessions. |
project_id | string | — | |
project_name | string | — | Project name — an alternative to project_id; resolved to the id internally. project_id wins if both are given. |
Parameters from the server's own tool schema.
Why list_sessions is rated Low
This tool queries and returns information about active sessions without creating, modifying, deleting, or executing any operations. It is purely informational and has no side effects on the system state. The [MAINTENANCE] prefix and read-only designation further confirm the benign nature of this operation.
From the tool's definition Tool description explicitly states 'Read-only: List active sessions for a project.' The verb 'List' and the lack of any modification capability confirm retrieval-only behavior.
Attacks that exploit this kind of access
The rule that runs list_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_sessions, this is the rule to start with:
list_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_sessions call is checked against it from then on.
Questions about list_sessions
[MAINTENANCE] Read-only: List active sessions for a project. Useful for planning chat to see what's currently running before filing new sprint items. It is categorised as a Read tool in the Meridian MCP Server, which means it retrieves data without modifying state.
list_sessions accepts 3 parameters: status, project_id, project_name. 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_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_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_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_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_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