Get the event history of a memory — creation, updates, promotions, and feedback. Use when you need to understand how a memory evolved or diagnose unexpected behavior.
AI agents call get_memory_history to retrieve information from Memsolus MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical metadata about a memory item (its creation date, update timestamps, promotion events, and feedback records). It performs no modifications, deletions, or external operations.
From the tool's definition Tool description states 'Get the event history of a memory' and lists read-only operations: 'creation, updates, promotions, and feedback.' The verb 'Get' and focus on retrieval and understanding indicate pure data querying with no side effects.
Attacks that exploit this kind of access
Get the event history of a memory — creation, updates, promotions, and feedback. Use when you need to understand how a memory evolved or diagnose unexpected behavior. It is categorised as a Read tool in the Memsolus MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Memsolus MCP Server MCP server in PolicyLayer and add a rule for get_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 Memsolus MCP Server. Nothing to install.
get_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 get_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 get_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.
get_memory_history is provided by the Memsolus MCP Server MCP server (memsolus/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 →