audit_history
Get the full audit history for a specific entity in chronological order
This record as markdown: /tools/danielsimonjr-memory-mcp/audit-history.md
What audit_history does on Enhanced Knowledge Graph Memory Server
AI agents call audit_history to retrieve information from Enhanced Knowledge Graph Memory Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why audit_history is rated Low
This is a straightforward audit log query that returns historical records of changes to a specific entity. Reading audit logs is a read-only operation with no capacity to modify data, execute operations, or cause financial impact. The blast radius of misuse is minimal—unauthorized access to audit history could reveal sensitive information about what changes were made, but cannot itself alter or delete data.
From the tool's definition Tool retrieves audit history in 'chronological order' with no modification or deletion capability mentioned. The verb 'Get' explicitly indicates data retrieval without side effects.
Attacks that exploit this kind of access
The rule that runs audit_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enhanced Knowledge Graph Memory Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For audit_history, this is the rule to start with:
audit_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Enhanced Knowledge Graph Memory Server, apply this rule, and every audit_history call is checked against it from then on.
Questions about audit_history
Get the full audit history for a specific entity in chronological order. It is categorised as a Read tool in the Enhanced Knowledge Graph Memory Server MCP Server, which means it retrieves data without modifying state.
Register the Enhanced Knowledge Graph Memory Server MCP server in PolicyLayer and add a rule for audit_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 Enhanced Knowledge Graph Memory Server. Nothing to install.
audit_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 audit_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 audit_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.
audit_history is provided by the Enhanced Knowledge Graph Memory Server MCP server (danielsimonjr/memory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enhanced Knowledge Graph Memory Server, and thousands of servers like it.
Across the catalogue