top_memories
Return the top N highest-priority non-expired keys in a namespace, ordered by priority descending. Useful for loading the most important context when space is limited. Maximum n is 1000.
This record as markdown: /tools/dev-aic0rt3x-memory-mcp/top-memories.md
What top_memories does on AI Cortex Storage
AI agents call top_memories to retrieve information from AI Cortex Storage without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
n | integer | — | Number of keys to return (default 10, max 1000) |
namespace | string | Yes | ≤ 255 characters, no '/' |
Parameters from the server's own tool schema.
Why top_memories is rated Low
This tool queries and retrieves existing memory data from a namespace with no side effects. It is a read-only operation that filters and orders data for display. The capability is limited to 1000 keys maximum, and there is no mechanism to alter state. While the associated server manages sensitive data (memories, API keys, payments), this specific tool only accesses and returns information without modifying it.
From the tool's definition Tool description states 'Return the top N highest-priority non-expired keys' and 'Useful for loading the most important context' — pure data retrieval with no modification, creation, or deletion of memories.
Attacks that exploit this kind of access
The rule that runs top_memories safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AI Cortex Storage, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For top_memories, this is the rule to start with:
top_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 AI Cortex Storage, apply this rule, and every top_memories call is checked against it from then on.
Questions about top_memories
Return the top N highest-priority non-expired keys in a namespace, ordered by priority descending. Useful for loading the most important context when space is limited. Maximum n is 1000. It is categorised as a Read tool in the AI Cortex Storage MCP Server, which means it retrieves data without modifying state.
top_memories accepts 2 parameters: n, namespace. Required: namespace. The full parameter table on this page comes from the server's own tool schema.
Register the AI Cortex Storage MCP server in PolicyLayer and add a rule for top_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 AI Cortex Storage. Nothing to install.
top_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 top_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 top_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.
top_memories is provided by the AI Cortex Storage MCP server (https://memory.aic0rt3x.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AI Cortex Storage, and thousands of servers like it.
This server
Across the catalogue