# memory.sweep

Retention: forget every fact the ledger learned of before an instant, in one space or all, skipping held facts, and remove each from every store. Without

Agent View of the PolicyLayer registry record for `memory.sweep`. HTML page: https://policylayer.com/tools/agent-custody/memory.sweep

## Facts

- Tool: `memory.sweep`
- Server: Agent Custody (`ch4r10t33r/agent-custody`) — https://policylayer.com/tools/agent-custody.md
- Homepage: https://github.com/ch4r10t33r/agent-custody
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "memory.sweep",
    "arguments": {}
  }
}
```

## Why memory.sweep is rated Critical

An AI agent that decides to call memory.sweep doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Agent Custody is gone. There is no undo for destructive operations.

Risk signals: Bulk/mass operation — affects multiple targets

## Use case

AI agents call memory.sweep to permanently remove resources in Agent Custody, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Agent Custody:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "memory.sweep"
  ]
}
```

## Other tools on Agent Custody (13)

- `memory.forget` — Destructive — https://policylayer.com/tools/agent-custody/memory.forget.md
- `customer.lookup` — Other — https://policylayer.com/tools/agent-custody/customer.lookup.md
- `echo.say` — Other — https://policylayer.com/tools/agent-custody/echo.say.md
- `memory.confirm` — Other — https://policylayer.com/tools/agent-custody/memory.confirm.md
- `memory.get` — Other — https://policylayer.com/tools/agent-custody/memory.get.md
- `memory.history` — Other — https://policylayer.com/tools/agent-custody/memory.history.md
- `memory.hold` — Other — https://policylayer.com/tools/agent-custody/memory.hold.md
- `memory.read` — Other — https://policylayer.com/tools/agent-custody/memory.read.md
- `memory.release` — Other — https://policylayer.com/tools/agent-custody/memory.release.md
- `memory.retract` — Other — https://policylayer.com/tools/agent-custody/memory.retract.md
- `stripe.payout` — Other — https://policylayer.com/tools/agent-custody/stripe.payout.md
- `stripe.refund` — Other — https://policylayer.com/tools/agent-custody/stripe.refund.md
- `memory.write` — Write — https://policylayer.com/tools/agent-custody/memory.write.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=agent-custody · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/agent-custody