memory_delete
Remove a stored memory entry by exact (namespace, key). Use when a previously stored decision is invalidated or contains stale data. No native equivalent — Write to a file does not affect the .swarm/memory.db SQLite store.
This record as markdown: /tools/hamza-agent-hub-252/memory-delete.md
What memory_delete does on Hamza Agent Hub 252
AI agents call memory_delete to permanently remove resources in Hamza Agent Hub 252, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why memory_delete is rated Critical
Although the data being deleted (agent memory entries) may be reconstructible or non-critical individually, the tool irreversibly removes records from a production database store. This is a classic destructive operation: once executed, the memory entry cannot be recovered without database backups.
From the tool's definition Tool performs 'Remove a stored memory entry' by deleting database records from '.swarm/memory.db SQLite store'.
Attacks that exploit this kind of access
The rule that runs memory_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Hamza Agent Hub 252, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory_delete, this is the rule to start with:
memory_delete 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 Hamza Agent Hub 252, apply this rule, and every memory_delete call is checked against it from then on.
Questions about memory_delete
Remove a stored memory entry by exact (namespace, key). Use when a previously stored decision is invalidated or contains stale data. No native equivalent — Write to a file does not affect the .swarm/memory.db SQLite store. It is categorised as a Destructive tool in the Hamza Agent Hub 252 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Hamza Agent Hub 252 MCP server in PolicyLayer and add a rule for memory_delete: 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 Hamza Agent Hub 252. Nothing to install.
memory_delete 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 memory_delete 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 memory_delete. 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.
memory_delete is provided by the Hamza Agent Hub 252 MCP server (hamzachallenge3-dev/hamza-agent-hub-252). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Hamza Agent Hub 252, and thousands of servers like it.
Across the catalogue