Get the full audit trail for a memory.
AI agents call memory_provenance to retrieve information from Claude Memory MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and retrieves an audit trail—a read-only operation with no side effects. While it may reveal sensitive historical information about memory modifications, this is informational access rather than destructive, executable, or financial action. The severity is low because audit trail retrieval itself does not alter system state or create irreversible consequences.
From the tool's definition Tool name 'memory_provenance' and description 'Get the full audit trail for a memory' indicate a retrieval operation that returns historical data without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Get the full audit trail for a memory. It is categorised as a Read tool in the Claude Memory MCP MCP Server, which means it retrieves data without modifying state.
Register the Claude Memory MCP server in PolicyLayer and add a rule for memory_provenance: 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 Memory MCP. Nothing to install.
memory_provenance 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_provenance 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_provenance. 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_provenance is provided by the Claude Memory MCP server (navid-kianfar/claude-memory-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 →