get_memory
Retrieve a stored value by namespace and key.
This record as markdown: /tools/dev-aic0rt3x-memory-mcp/get-memory.md
What get_memory does on AI Cortex Storage
AI agents call get_memory 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 |
|---|---|---|---|
key | string | Yes | ≤ 255 characters, no '/' |
namespace | string | Yes | ≤ 255 characters, no '/' |
Parameters from the server's own tool schema.
Why get_memory is rated Low
This tool queries and returns existing data without creating, modifying, deleting, or executing any operations. It has minimal blast radius—misuse would only expose stored memories, not alter system state or cause irreversible damage.
From the tool's definition Tool name is 'get_memory' and description states 'Retrieve a stored value by namespace and key.' The verb 'retrieve' and absence of any modification language indicate a read-only operation.
Attacks that exploit this kind of access
The rule that runs get_memory 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 get_memory, this is the rule to start with:
get_memory 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 get_memory call is checked against it from then on.
Questions about get_memory
Retrieve a stored value by namespace and key. It is categorised as a Read tool in the AI Cortex Storage MCP Server, which means it retrieves data without modifying state.
get_memory accepts 2 parameters: key, namespace. Required: key, 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 get_memory: 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.
get_memory 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 get_memory 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 get_memory. 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.
get_memory 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