View the chronological audit trail of changes to memory. Returns a timeline of writes, updates, deletes, namespace deletes, and log appends. Use this to answer
AI agents call memory_history to retrieve information from Munin Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
memory_history retrieves historical data from the memory system without modifying, deleting, or executing any code. It is purely informational — examining an audit trail is a read-only operation. The low severity reflects minimal blast radius: viewing history cannot damage data or trigger unintended side effects.
From the tool's definition Tool description states 'View the chronological audit trail' and 'Returns a timeline' — these are passive retrieval operations. No mutations, deletions, or external operations occur.
Attacks that exploit this kind of access
View the chronological audit trail of changes to memory. Returns a timeline of writes, updates, deletes, namespace deletes, and log appends. Use this to answer. It is categorised as a Read tool in the Munin Memory MCP Server, which means it retrieves data without modifying state.
Register the Munin Memory 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 Munin Memory. 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 Munin Memory MCP server (magnus-gille/munin-memory). 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 →