get_session_history

프로젝트의 세션 이력을 조회합니다.

Server Claude Session Continuity leesgit/claude-session-continuity-mcp
Category Read
Risk class Low
Parameters 00 required

What get_session_history does on Claude Session Continuity

AI agents call get_session_history to retrieve information from Claude Session Continuity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_session_history needs a policy

This tool retrieves historical session data for a project without modifying, deleting, or executing any operations. It is a read-only query function that fits the Read category. Severity is low because session history metadata poses minimal risk even if exposed to an AI agent—the blast radius is limited to information disclosure of past context, not operational impact.

From the tool's definition Tool name 'get_session_history' and description '프로젝트의 세션 이력을 조회합니다' (retrieves project session history) indicate a query/retrieval operation with no side effects.

Questions about get_session_history

What does the get_session_history tool do? +

프로젝트의 세션 이력을 조회합니다. It is categorised as a Read tool in the Claude Session Continuity MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_session_history? +

Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for get_session_history: 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 Claude Session Continuity. Nothing to install.

What risk level is get_session_history? +

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

Can I rate-limit get_session_history? +

Yes. Add a rate_limit block to the get_session_history 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 get_session_history completely? +

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

get_session_history is provided by the Claude Session Continuity MCP server (leesgit/claude-session-continuity-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

get_session_history is one line of Claude Session Continuity's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

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.