Associate a Claude session ID with *name* for future --resume support.
AI agents use session_set_claude_id to create or update resources in Claude Code — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Code environment.
The tool creates or updates a session identifier association, which is a write operation that modifies system state (the session registry or lookup table). It is not destructive since the association can be changed or deleted, and it has no immediate side effects on code execution or data deletion.
From the tool's definition Tool description states it will 'Associate a Claude session ID with *name*', which creates or modifies a mapping/association for future session resumption. This is a metadata write operation.
Attacks that exploit this kind of access
Associate a Claude session ID with *name* for future --resume support. It is categorised as a Write tool in the Claude Code MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Code MCP server in PolicyLayer and add a rule for session_set_claude_id: 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 Code. Nothing to install.
session_set_claude_id 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 session_set_claude_id 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 session_set_claude_id. 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.
session_set_claude_id is provided by the Claude Code MCP server (joschi655/claude-code-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 →