forget
Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall.
This record as markdown: /tools/io-github-pipeworx-io-19hz/forget.md
What forget does on 19hz
AI agents call forget to permanently remove resources in 19hz, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
key | string | Yes | Memory key to delete |
Parameters from the server's own tool schema.
Why forget is rated Critical
This tool irreversibly deletes data (stored memories) with no undo capability. Although the data being deleted is application-level memory rather than a database, the destructive nature of the operation—permanent removal without recovery—places it in the Destructive category. The high severity reflects that an agent could inadvertently clear important context or sensitive information the user intended to preserve.
From the tool's definition "Delete a previously stored memory by key" — the tool explicitly performs deletion of stored data with no mechanism to recover or undo the operation.
Attacks that exploit this kind of access
The rule that runs forget 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 forget, this is the rule to start with:
forget is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 19hz, apply this rule, and every forget call is checked against it from then on.
Questions about forget
Delete a previously stored memory by key. Use when context is stale, the task is done, or you want to clear sensitive data the agent saved earlier. Pair with remember and recall. It is categorised as a Destructive tool in the 19hz MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
forget accepts 1 parameter: key. Required: key. 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 forget: 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.
forget is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the forget 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 forget. 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.
forget 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.
Across the catalogue