GLOBAL: List ALL projects that have Claude Code session history. This server has access to sessions from ALL projects, not just the current one.
AI agents call sessions_projects 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 project metadata from session history. It has no side effects, cannot modify data, execute code, or cause financial impact. The 'GLOBAL' scope expands access but does not change the fundamental read-only nature of the operation. Severity is low because listing projects causes no harm even if misused by an agent; blast radius is minimal.
From the tool's definition Tool name and description indicate retrieval only: 'List ALL projects' and 'search and browse Claude Code conversation history' — no creation, modification, deletion, or execution described.
Attacks that exploit this kind of access
GLOBAL: List ALL projects that have Claude Code session history. This server has access to sessions from ALL projects, not just the current one. 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_projects: 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_projects 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_projects 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_projects. 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_projects 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 →