List pending memory candidates waiting for developer approval.
AI agents call list_memory_candidates 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 and displays information about pending memory candidates without creating, modifying, deleting, or executing anything. It is purely informational—a query operation to view the state of candidates awaiting approval. There is minimal risk as it merely exposes existing data without triggering any external operations or modifications.
From the tool's definition Tool name is 'list_memory_candidates' and description states it 'List[s] pending memory candidates waiting for developer approval.' The verb 'list' and action of retrieving/querying pending candidates indicates a read-only operation with no side effects.
Attacks that exploit this kind of access
List pending memory candidates waiting for developer approval. 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_memory_candidates: 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_memory_candidates 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_memory_candidates 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_memory_candidates. 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_memory_candidates 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 →