// SCAN REPORT

Brain

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

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

Last updated: 12 Jun 2026

5 can modify or destroy data

5 read-only

10 tools total

Community server · catalogue entry verified 12/06/2026

How to control Brain ↓

TOOL MAP

What Brain exposes to your agents

Read (5) Write / Execute (5) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Brain tools

Execute · Medium reindex_tool Based on the name, this tool likely triggers a reindexing operation of the note corpus (rebuilding search indexes). Write · Low create_note_tool A tool that creates notes in a private Markdown knowledge base creates or modifies data reversibly. Write · Medium save_conversation_tool Based on the name and server context, this tool most likely creates or modifies persistent data (saving conversations as notes). Write · Medium append_to_note_tool The tool name strongly suggests appending (adding) content to an existing Markdown note, which is a reversible write operation.

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

POLICY

How to control Brain

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

Rate limit write operations

{
  "append_to_note_tool": {
    "limits": [
      {
        "counter": "append_to_note_tool_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "hybrid_search_tool": {
    "limits": [
      {
        "counter": "hybrid_search_tool_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 Brain — 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 BRAIN →

Free to start. No card required.

FULL CATALOGUE

All 10 Brain tools

EXECUTE 1 tools

Execute reindex_tool reindex_tool

WRITE 4 tools

Write append_to_note_tool append_to_note_tool Write ingest_file_tool ingest_file_tool Write create_note_tool create_note_tool Write save_conversation_tool save_conversation_tool

READ 5 tools

Read hybrid_search_tool hybrid_search_tool Read keyword_search_tool keyword_search_tool Read list_recent_tool list_recent_tool Read read_note_tool read_note_tool Read semantic_search_tool semantic_search_tool

FAQ

Questions about Brain

How do I prevent bulk modifications through Brain? +

The Brain server has 4 write tools including append_to_note_tool, ingest_file_tool, create_note_tool. 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 Brain.

How many tools does the Brain MCP server expose? +

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

How do I enforce a policy on Brain? +

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

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

ENFORCE POLICY ON BRAIN →

Free to start. No card required.

10 Brain tools catalogued and risk-classified — across an index of 43,000+ MCP servers.