Return recent OpenMembrane audit events for memory pipeline activity.
AI agents call list_audit_log to retrieve information from OpenMemBrain without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves audit log entries documenting memory pipeline activity. It performs a pure read operation—querying existing historical data without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal; an AI agent could only access audit information already recorded by the system, which has no direct consequences beyond potential information disclosure.
From the tool's definition Tool name 'list_audit_log' and description 'Return recent OpenMembrane audit events' indicate retrieval and querying of historical log data with no modification or side effects.
Attacks that exploit this kind of access
Return recent OpenMembrane audit events for memory pipeline activity. It is categorised as a Read tool in the OpenMemBrain MCP Server, which means it retrieves data without modifying state.
Register the OpenMemBrain MCP server in PolicyLayer and add a rule for list_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 OpenMemBrain. Nothing to install.
list_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 list_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 list_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.
list_audit_log is provided by the OpenMemBrain MCP server (mohamadalhusseinie/openmembrain). 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 →