GLOBAL: Search Claude Code sessions by keyword across ANY or ALL projects. Has access to conversation history from all projects.
AI agents call sessions_search to retrieve information from Mcp Sessions without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves conversation history data across projects without side effects. However, it warrants 'medium' severity rather than 'low' because unrestricted search across ALL projects could expose sensitive conversation content (debugging details, API keys, proprietary code, private thoughts) if an AI agent misuses the GLOBAL scope or keyword parameters to extract confidential information.
From the tool's definition Tool description states it 'Search[es] Claude Code sessions by keyword' and provides 'access to conversation history'—purely retrieval operations with no modification or execution capability.
Attacks that exploit this kind of access
GLOBAL: Search Claude Code sessions by keyword across ANY or ALL projects. Has access to conversation history from all projects. It is categorised as a Read tool in the Mcp Sessions MCP Server, which means it retrieves data without modifying state.
Register the Mcp Sessions MCP server in PolicyLayer and add a rule for sessions_search: 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 Mcp Sessions. Nothing to install.
sessions_search 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 sessions_search 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 sessions_search. 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.
sessions_search is provided by the Mcp Sessions MCP server (yurich-ru/mcp-sessions). 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 →