store_memory
Persist a value across your instances: PUT /memory/{ns}/{key}. Optionally set ttl (seconds, min 60, max 30 days) for auto-eviction. Values survive until evicted or manually deleted.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/store-memory.md
What store_memory does on Gateway
AI agents use store_memory to create or update resources in Gateway, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gateway environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | entry name |
ttl | integer | — | seconds until auto-eviction (60–2_592_000, omit=permanent) |
value | object | Yes | any JSON value |
handle | string | — | |
secret | string | — | |
namespace | string | Yes | logical grouping (e.g. 'projects') |
Parameters from the server's own tool schema.
Why store_memory is rated Medium
This tool creates and modifies data in a memory/state store that persists across agent instances. While the operation is reversible (can be deleted or auto-evicted), unauthorized or erroneous writes could corrupt agent state, cause logic errors, or interfere with other agent instances sharing the same namespace.
From the tool's definition Tool description states 'Persist a value' and 'PUT /memory/{ns}/{key}', indicating creation/modification of data in a persistent store. The ability to 'set ttl' for 'auto-eviction' and 'manually deleted' confirms reversible data manipulation.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs store_memory safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For store_memory, this is the rule to start with:
store_memory stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every store_memory call is checked against it from then on.
Questions about store_memory
Persist a value across your instances: PUT /memory/{ns}/{key}. Optionally set ttl (seconds, min 60, max 30 days) for auto-eviction. Values survive until evicted or manually deleted. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
store_memory accepts 6 parameters: key, ttl, value, handle, secret, namespace. Required: key, value, namespace. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for store_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 Gateway. Nothing to install.
store_memory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the store_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 store_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.
store_memory is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue