// SCAN REPORT

Squish Memory

4 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

1 can modify or destroy data

3 read-only

4 tools total

Community server · catalogue entry verified 29/06/2026

How to control Squish Memory ↓

TOOL MAP

What Squish Memory exposes to your agents

Read (3) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Squish Memory tools

Write · Medium squish_remember This tool writes (stores) information to a shared memory store that persists across sessions and AI agents.

1 of Squish Memory's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Squish Memory

PolicyLayer is an MCP gateway — it sits between your AI agents and Squish Memory, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "squish_remember": {
    "limits": [
      {
        "counter": "squish_remember_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "squish_context": {
    "limits": [
      {
        "counter": "squish_context_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Squish Memory — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON SQUISH MEMORY →

Instant setup, no code required.

FULL CATALOGUE

All 4 Squish Memory tools

WRITE 1 tools

Write squish_remember Remember a memory for future context

READ 3 tools

Read squish_context Inject memory context into current session Read squish_recall Recall memories by search query Read squish_stats Get memory statistics

FAQ

Questions about Squish Memory

How do I prevent bulk modifications through Squish Memory? +

The Squish Memory server has 1 write tools including squish_remember. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Squish Memory.

How many tools does the Squish Memory MCP server expose? +

4 tools across 1 categories: Read. 3 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Squish Memory? +

Register the Squish Memory MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Squish Memory tool call.

Deterministic rules across all 4 Squish Memory tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON SQUISH MEMORY →

Instant setup, no code required.

4 Squish Memory tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Squish Memory's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →