Access and analyze the history of reasoning sessions to find
AI agents call reasoning_history to retrieve information from EPH-MCP: Emergent Pattern Hunter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical data about reasoning sessions for analysis purposes. There are no indications of data creation, modification, deletion, code execution, or financial operations. The incomplete description ('find' without completion) does not suggest destructive or execute capabilities.
From the tool's definition Tool name is 'reasoning_history' and description states 'Access and analyze the history of reasoning sessions to find' — uses 'access' and 'analyze', indicating data retrieval without modification.
Attacks that exploit this kind of access
Access and analyze the history of reasoning sessions to find. It is categorised as a Read tool in the EPH-MCP: Emergent Pattern Hunter MCP Server, which means it retrieves data without modifying state.
Register the EPH-MCP: Emergent Pattern Hunter MCP server in PolicyLayer and add a rule for reasoning_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 EPH-MCP: Emergent Pattern Hunter. Nothing to install.
reasoning_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 reasoning_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 reasoning_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.
reasoning_history is provided by the EPH-MCP: Emergent Pattern Hunter MCP server (psikosen/eph_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 →