list_memories
List all memories with optional filtering. Best practice: set an active project first to avoid mixing contexts from different workspaces. Use default (full_text=false) for quick browsing; set full_text=true only when you need complete content. For many items, consider using search_memory with rel...
This record as markdown: /tools/0xrelogic-cognio/list-memories.md
What list_memories does on Cognio
AI agents call list_memories to retrieve information from Cognio without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_memories is rated Low
This tool retrieves and queries memory data without any side effects. The description emphasizes it is for 'quick browsing' and explicitly recommends alternatives for searching, confirming it performs read-only operations. The optional 'full_text' parameter controls output verbosity but does not modify underlying data. No data creation, modification, deletion, or execution occurs.
From the tool's definition Tool name is 'list_memories' and description states it 'List all memories with optional filtering' and recommends using 'search_memory' for querying content, indicating this is a retrieval operation with no modification capability.
Attacks that exploit this kind of access
The rule that runs list_memories safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cognio, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_memories, this is the rule to start with:
list_memories is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cognio, apply this rule, and every list_memories call is checked against it from then on.
Questions about list_memories
List all memories with optional filtering. Best practice: set an active project first to avoid mixing contexts from different workspaces. Use default (full_text=false) for quick browsing; set full_text=true only when you need complete content. For many items, consider using search_memory with relevant keywords instead. It is categorised as a Read tool in the Cognio MCP Server, which means it retrieves data without modifying state.
Register the Cognio 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 Cognio. 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 Cognio MCP server (0xrelogic/cognio). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cognio, and thousands of servers like it.
This server
Across the catalogue