実行履歴を取得
AI agents call get_execution_history 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 queries and returns execution history from stored context. It is purely informational—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an attacker could only view historical execution records, not alter systems or access unrelated data beyond what the server manages. This is a typical Read operation.
From the tool's definition Tool name 'get_execution_history' and description '実行履歴を取得' (retrieve execution history) indicate a retrieval operation with no side effects. The function retrieves historical data without modifying, deleting, or executing anything.
Attacks that exploit this kind of access
実行履歴を取得. 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_execution_history: 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_execution_history 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_execution_history 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_execution_history. 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_execution_history 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 →