remember
Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped ...
This record as markdown: /tools/io-github-pipeworx-io-19hz/remember.md
What remember does on 19hz
AI agents use remember to create or update resources in 19hz, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your 19hz environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Memory key (e.g., "subject_property", "target_ticker", "user_preference") |
value | string | Yes | Value to store (any text — findings, addresses, preferences, notes) |
Parameters from the server's own tool schema.
Why remember is rated Medium
The tool creates/writes persistent key-value data that survives across sessions. It is reversible (paired with 'forget' to delete), so Write is appropriate rather than Destructive. Misuse could lead to storing sensitive or manipulated data persistently, giving it medium severity.
From the tool's definition Save data the agent will need to reuse later — stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory.
Attacks that exploit this kind of access
The rule that runs remember safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 19hz, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remember, this is the rule to start with:
remember 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 19hz, apply this rule, and every remember call is checked against it from then on.
Questions about remember
Save data the agent will need to reuse later — across this conversation or across sessions. Use when you discover something worth carrying forward (a resolved ticker, a target address, a user preference, a research subject) so you don't have to look it up again. Stored as a key-value pair scoped by your identifier. Authenticated users get persistent memory; anonymous sessions retain memory for 24 hours. Pair with recall to retrieve later, forget to delete. It is categorised as a Write tool in the 19hz MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
remember accepts 2 parameters: key, value. Required: key, value. The full parameter table on this page comes from the server's own tool schema.
Register the 19hz MCP server in PolicyLayer and add a rule for remember: 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 19hz. Nothing to install.
remember 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 remember 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 remember. 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.
remember is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 19hz, and thousands of servers like it.
This server
Across the catalogue