Retrieve all versions of a logical memory. Pass any version ID in the chain.
AI agents call memory_history to retrieve information from Claude Crowed without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical versions of stored memory documents. It queries and returns data without side effects—no data is created, modified, deleted, or executed. The low severity reflects that accessing version history of semantic memory poses minimal risk even if misused by an agent; it cannot alter data or trigger external operations.
From the tool's definition Tool name 'memory_history' and description 'Retrieve all versions of a logical memory' indicate a read-only operation. The verb 'Retrieve' and the passive context of version history access show no modification, deletion, or execution of code/commands.
Attacks that exploit this kind of access
Retrieve all versions of a logical memory. Pass any version ID in the chain. It is categorised as a Read tool in the Claude Crowed MCP Server, which means it retrieves data without modifying state.
Register the Claude Crowed MCP server in PolicyLayer and add a rule for memory_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 Claude Crowed. Nothing to install.
memory_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 memory_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 memory_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.
memory_history is provided by the Claude Crowed MCP server (thenewjavaman/claude-crowed). 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 →