GLOBAL: Get git commits made during a session
AI agents call session_diff 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 historical git commit data from a session without creating, modifying, deleting, or executing anything. It is purely informational retrieval. Severity is low because viewing commit history poses minimal security risk—the commits themselves were already recorded in git, and this tool merely surfaces that existing information.
From the tool's definition Tool description states 'Get git commits made during a session' — a retrieval operation with no modification or execution capability. The verb 'Get' and context of browsing conversation history confirm read-only semantics.
Attacks that exploit this kind of access
GLOBAL: Get git commits made during a session. 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_diff: 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_diff 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_diff 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_diff. 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_diff 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 →