프로젝트의 plan.md에서 기술 스택 정보를 추출합니다.
AI agents call get_tech_stack 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.
The tool performs a read-only query of static project documentation (plan.md) to retrieve technical stack metadata. No data is created, modified, deleted, or executed. This is a straightforward data retrieval operation with minimal blast radius if misused by an agent.
From the tool's definition Tool description states it 'extracts technology stack information from project's plan.md' — a retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
프로젝트의 plan.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_tech_stack: 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_tech_stack 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_tech_stack 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_tech_stack. 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_tech_stack 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 →