GLOBAL: Find sessions that mention a specific file path, across ANY or ALL projects.
AI agents call sessions_by_file 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 performs a query/search operation across conversation history to locate mentions of a file path. It retrieves data with no side effects, no code execution, no data modification, and no destructive actions. The primary risk is information disclosure if an agent queries sensitive file paths, but this is a low-severity read operation typical of search/browse functionality.
From the tool's definition Tool description explicitly states 'Find sessions that mention a specific file path' and is positioned alongside read-only operations (session_diff, session_messages, session_summary, sessions_list, sessions_search).
Attacks that exploit this kind of access
GLOBAL: Find sessions that mention a specific file path, across ANY or 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_by_file: 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_by_file 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_by_file 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_by_file. 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_by_file 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 →