現在のセッションIDを取得
AI agents call get_current_session to retrieve information from MCP Claude Context Continuity without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves session metadata (the current session ID) with no side effects, no code execution, no data modification, and no destructive operations. It is a simple read operation that queries existing state. The low severity reflects that unauthorized access to a session ID alone poses minimal direct risk in this context continuity management system.
From the tool's definition Tool name 'get_current_session' and description '現在のセッションIDを取得' (Get the current session ID) indicate a retrieval operation that queries and returns the current session identifier without modifying any state.
Attacks that exploit this kind of access
現在のセッションIDを取得. It is categorised as a Read tool in the MCP Claude Context Continuity MCP Server, which means it retrieves data without modifying state.
Register the MCP Claude Context Continuity MCP server in PolicyLayer and add a rule for get_current_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 MCP Claude Context Continuity. Nothing to install.
get_current_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_current_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_current_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_current_session is provided by the MCP Claude Context Continuity MCP server (tethiro/mcp-claude-context-continuity). 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 →