list_keys
List keys in a namespace with metadata (created_at, updated_at, updated_count, ttl, priority, last_modified_key_id). Returns up to 1000 keys sorted by recency. Expired keys are automatically excluded.
This record as markdown: /tools/dev-aic0rt3x-memory-mcp/list-keys.md
What list_keys does on AI Cortex Storage
AI agents call list_keys 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 |
|---|---|---|---|
namespace | string | Yes | ≤ 255 characters, no '/' |
Parameters from the server's own tool schema.
Why list_keys is rated Low
This tool retrieves and queries key metadata from a namespace without creating, modifying, deleting, or executing operations. It is a straightforward data retrieval function with no destructive or reversible side effects. Severity is low because listing metadata poses minimal risk; an AI agent cannot cause significant harm by querying key names and their timestamps.
From the tool's definition Tool description explicitly states it 'List keys in a namespace' and 'Returns' metadata about keys. The verb 'list' combined with read-only output (created_at, updated_at timestamps, metadata) confirms retrieval-only behavior with no side effects.
Attacks that exploit this kind of access
The rule that runs list_keys 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 list_keys, this is the rule to start with:
list_keys 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 list_keys call is checked against it from then on.
Questions about list_keys
List keys in a namespace with metadata (created_at, updated_at, updated_count, ttl, priority, last_modified_key_id). Returns up to 1000 keys sorted by recency. Expired keys are automatically excluded. It is categorised as a Read tool in the AI Cortex Storage MCP Server, which means it retrieves data without modifying state.
list_keys accepts 1 parameter: 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 list_keys: 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.
list_keys 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_keys 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_keys. 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_keys 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