Medium Risk

memory_snooze

Temporarily hide a memory from context surfacing. USE PROACTIVELY when vault-context repeatedly surfaces irrelevant content — snooze it for 30 days instead of ignoring it. Reduces noise for future sessions.

How to control memory_snooze ↓

AI agents use memory_snooze to create or update resources in ClawMem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ClawMem environment.

Medium Risk

This tool modifies the state of a memory entry by suppressing it from retrieval for a defined period (30 days). It is reversible — the memory is hidden, not deleted — so it falls under Write rather than Destructive. Misuse by an AI agent could cause important context to be silenced across sessions, giving it a medium severity blast radius.

From the tool's definition Temporarily hide a memory from context surfacing... snooze it for 30 days instead of ignoring it

Documented attack patterns abuse exactly the kind of access memory_snooze gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and ClawMem, and nothing reaches the server without passing your rules. This is the rule we recommend for memory_snooze:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "memory_snooze": {
      "limits": [
        {
          "counter": "memory_snooze_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

memory_snooze 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.

  1. Create a free account and register ClawMem — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the memory_snooze tool do? +

Temporarily hide a memory from context surfacing. USE PROACTIVELY when vault-context repeatedly surfaces irrelevant content — snooze it for 30 days instead of ignoring it. Reduces noise for future sessions. It is categorised as a Write tool in the ClawMem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on memory_snooze? +

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

What risk level is memory_snooze? +

memory_snooze is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit memory_snooze? +

Yes. Add a rate_limit block to the memory_snooze 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_snooze completely? +

Set action: deny in the PolicyLayer policy for memory_snooze. 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_snooze? +

memory_snooze is provided by the ClawMem MCP server (yoloshii/clawmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every ClawMem tool call.

Deterministic rules across all 30 ClawMem tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

30 ClawMem tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.