프로젝트의 활성 컨텍스트를 업데이트합니다. 작업 종료 시 호출.
AI agents use update_active_context to create or update resources in Claude Session Continuity — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Session Continuity environment.
The tool creates or modifies project context data (session continuity system) but does not delete or destroy data irreversibly. It is a Write operation that updates session state to enable context restoration.
From the tool's definition Tool name 'update_active_context' and description state it 'updates' project's active context, called when ending a task. This modifies stored session state reversibly.
Attacks that exploit this kind of access
프로젝트의 활성 컨텍스트를 업데이트합니다. 작업 종료 시 호출. It is categorised as a Write tool in the Claude Session Continuity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Session Continuity MCP server in PolicyLayer and add a rule for update_active_context: 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.
update_active_context is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_active_context 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 update_active_context. 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.
update_active_context 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 →