List all saved reasoning sessions with optional filtering.
AI agents call deep_list_sessions to retrieve information from Deep Reasoning without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a read-only operation that retrieves and filters data about saved sessions. It has no side effects, does not modify, create, or delete sessions, and does not execute code or trigger external operations. This is a straightforward data retrieval function matching the 'Read' category definition.
From the tool's definition Tool name 'deep_list_sessions' and description 'List all saved reasoning sessions with optional filtering' indicate a retrieval operation that queries existing sessions without modification or deletion.
Attacks that exploit this kind of access
List all saved reasoning sessions with optional filtering. It is categorised as a Read tool in the Deep Reasoning MCP Server, which means it retrieves data without modifying state.
Register the Deep Reasoning MCP server in PolicyLayer and add a rule for deep_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 Deep Reasoning. Nothing to install.
deep_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 deep_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 deep_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.
deep_list_sessions is provided by the Deep Reasoning MCP server (mauriziomocci/deep-reasoning-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →