List all memories Args: user_id: User identifier agent_id: Agent identifier run_id: Run/session identifier limit: Maximum number of results (default 100) offset: Offset (default 0) filters: Metadata filters Returns: JSON formatted string
AI agents call list_memories to retrieve information from Mcp Oceanbase without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries memory data without creating, modifying, deleting, or executing operations. It is a straightforward read operation with no destructive or side-effect capability. Severity is low because reading memory metadata has minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name is 'list_memories' and description states 'List all memories'. The arguments (user_id, agent_id, run_id, limit, offset, filters) are all read-only query parameters.
Documented attack patterns abuse exactly the kind of access list_memories gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Oceanbase, and nothing reaches the server without passing your rules. This is the rule we recommend for list_memories:
{
"version": "1",
"default": "deny",
"tools": {
"list_memories": {}
}
}list_memories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all memories Args: user_id: User identifier agent_id: Agent identifier run_id: Run/session identifier limit: Maximum number of results (default 100) offset: Offset (default 0) filters: Metadata filters Returns: JSON formatted string. It is categorised as a Read tool in the Mcp Oceanbase MCP Server, which means it retrieves data without modifying state.
Register the Mcp Oceanbase MCP server in PolicyLayer and add a rule for list_memories: 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 Mcp Oceanbase. Nothing to install.
list_memories 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_memories 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_memories. 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_memories is provided by the Mcp Oceanbase MCP server (oceanbase/awesome-oceanbase-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 134 Mcp Oceanbase tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
134 Mcp Oceanbase tools catalogued and risk-classified — across an index of 42,500+ MCP servers.