프로젝트의 SESSION.md를 파싱하여 구조화된 데이터로 반환합니다.
AI agents call get_session 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.
This tool retrieves and reads session context data from a markdown file, transforming it into structured format. It performs no mutations, deletions, or external operations. The blast radius of misuse is minimal—an agent could only read previously captured session state, which poses no irreversible harm or financial risk.
From the tool's definition Tool description states it 'parses PROJECT_SESSION.md and returns structured data' (파싱하여 구조화된 데이터로 반환합니다). The verb 'get_session' and 'parses...returns' indicate retrieval and querying of existing session metadata with no modifications or side effects.
Attacks that exploit this kind of access
프로젝트의 SESSION.md를 파싱하여 구조화된 데이터로 반환합니다. It is categorised as a Read tool in the Claude Session Continuity MCP Server, which means it retrieves data without modifying state.
Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for get_session: 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.
get_session 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 get_session 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 get_session. 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.
get_session 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.
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 →