// SCAN REPORT

Memory Bank

5 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 26 Jun 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 26/06/2026

How to control Memory Bank ↓

TOOL MAP

What Memory Bank exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Memory Bank tools

Write · Medium memory_bank_update The tool modifies existing data (memory bank files) in a reversible manner. Write · Medium memory_bank_write This tool creates new data (memory bank files) in a reversible manner.

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

POLICY

How to control Memory Bank

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

Rate limit write operations

{
  "memory_bank_update": {
    "limits": [
      {
        "counter": "memory_bank_update_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "list_project_files": {
    "limits": [
      {
        "counter": "list_project_files_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 Memory Bank — 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 MEMORY BANK →

Instant setup, no code required.

FULL CATALOGUE

All 5 Memory Bank tools

WRITE 2 tools

Write memory_bank_update Update an existing memory bank file for a specific project Write memory_bank_write Create a new memory bank file for a specific project

READ 3 tools

Read list_project_files List all files within a specific project Read list_projects List all projects in the memory bank Read memory_bank_read Read a memory bank file for a specific project

FAQ

Questions about Memory Bank

How do I prevent bulk modifications through Memory Bank? +

The Memory Bank server has 2 write tools including memory_bank_update, memory_bank_write. 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 Memory Bank.

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

5 tools across 2 categories: Read, Write. 3 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Memory Bank? +

Register the Memory Bank 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 Memory Bank tool call.

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

ENFORCE POLICY ON MEMORY BANK →

Instant setup, no code required.

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