memory.release

Lift a legal hold.

SERVERAgent Custody SOURCEch4r10t33r/agent-custody

Low RISK CLASS

Category Other

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/agent-custody/memory.release.md

WHAT IT DOES

What memory.release does on Agent Custody

AI agents call memory.release as a supporting operation in Agent Custody workflows.

RISK

Why memory.release is rated Low

Without any rule in front of it, every call an agent makes to memory.release happens silently: no trail, no cap, no way to know it misbehaved until something breaks downstream.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs memory.release safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Agent Custody, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For memory.release, this is the rule to start with:

memory.release Rate-limited

memory.release gets a rate cap, and everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory.release": {
      "limits": [
        {
          "counter": "memory.release_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

SET A RULE FOR THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Agent Custody, apply this rule, and every memory.release call is checked against it from then on.

FAQ

Questions about memory.release

What does the memory.release tool do? +

Lift a legal hold. It is categorised as a Other tool in the Agent Custody MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on memory.release? +

Register the Agent Custody MCP server in PolicyLayer and add a rule for memory.release: 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 Agent Custody. Nothing to install.

What risk level is memory.release? +

memory.release is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit memory.release? +

Yes. Add a rate_limit block to the memory.release 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.

How do I block memory.release completely? +

Set action: deny in the PolicyLayer policy for memory.release. 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.

What MCP server provides memory.release? +

memory.release is provided by the Agent Custody MCP server (ch4r10t33r/agent-custody). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Agent Custody, and thousands of servers like it.

This server

All 14 Agent Custody tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Tool risk categories →MCP tool →