session_summary

GLOBAL: Get session overview from ANY project: dates, message count, first/last user message, files mentioned.

Server Mcp Sessions yurich-ru/mcp-sessions
Category Read
Risk class Low
Parameters 00 required

What session_summary does on Mcp Sessions

AI agents call session_summary 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.

Why session_summary needs a policy

This tool retrieves historical metadata about Claude Code sessions without creating, modifying, deleting, or executing any operations. It performs a read-only query across conversation history.

From the tool's definition Tool description indicates it 'Get[s] session overview' with retrieval of metadata (dates, message count, files mentioned) with no modification capability indicated.

Questions about session_summary

What does the session_summary tool do? +

GLOBAL: Get session overview from ANY project: dates, message count, first/last user message, files mentioned. It is categorised as a Read tool in the Mcp Sessions MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on session_summary? +

Register the Mcp Sessions MCP server in PolicyLayer and add a rule for session_summary: 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.

What risk level is session_summary? +

session_summary is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit session_summary? +

Yes. Add a rate_limit block to the session_summary 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.

How do I block session_summary completely? +

Set action: deny in the PolicyLayer policy for session_summary. 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.

What MCP server provides session_summary? +

session_summary 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.