GLOBAL: Get raw messages from a session in ANY project, optionally filtered by query.
AI agents call session_messages 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 retrieves conversation messages from past sessions without modifying, deleting, or executing operations. The 'GLOBAL' scope indicates broad access to conversation history across projects, but this remains a read operation.
From the tool's definition Tool description states 'Get raw messages from a session' which retrieves/queries data. The word 'Get' combined with 'search and browse Claude Code conversation history' in server description indicates a read-only operation.
Attacks that exploit this kind of access
GLOBAL: Get raw messages from a session in ANY project, optionally filtered by query. 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 session_messages: 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.
session_messages 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 session_messages 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 session_messages. 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.
session_messages 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 →