List memory candidates currently waiting for governance review.
AI agents call memory.inbox_list to retrieve information from Lore Context without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries a list of pending memory items for review purposes. It does not create, modify, delete, execute commands, or move funds. The operation is a simple enumeration of existing governance queue items, consistent with the Read category for data retrieval without side effects.
From the tool's definition Tool name and description: 'List memory candidates currently waiting for governance review.' The verb 'list' and the passive framing 'waiting for review' indicate a read-only query operation with no mutation or side effects.
Attacks that exploit this kind of access
List memory candidates currently waiting for governance review. It is categorised as a Read tool in the Lore Context MCP Server, which means it retrieves data without modifying state.
Register the Lore Context MCP server in PolicyLayer and add a rule for memory.inbox_list: 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 Lore Context. Nothing to install.
memory.inbox_list 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.inbox_list 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.inbox_list. 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.inbox_list is provided by the Lore Context MCP server (Lore-Context/lore-context). 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 →