Query the write audit trail for a vault. Filterable by note path, operation type, or time. Default limit 50.
AI agents call audit_log to retrieve information from Vault Memory without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries (reads) an existing audit log without modifying any data. It retrieves historical records of write operations but does not itself perform any writes, executions, or destructive actions. Severity is low because misuse would only expose audit metadata.
From the tool's definition Query the write audit trail for a vault. Filterable by note path, operation type, or time.
Attacks that exploit this kind of access
Query the write audit trail for a vault. Filterable by note path, operation type, or time. Default limit 50. It is categorised as a Read tool in the Vault Memory MCP Server, which means it retrieves data without modifying state.
Register the Vault Memory MCP server in PolicyLayer and add a rule for audit_log: 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 Vault Memory. Nothing to install.
audit_log 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_log 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_log. 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_log is provided by the Vault Memory MCP server (owrede/vault-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 →