Infinite Context Keeper

17 tools. 7 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

7 can modify or destroy data
10 read-only
17 tools total

Community server · catalogue entry verified 29/06/2026

How to control Infinite Context Keeper ↓

What Infinite Context Keeper exposes to your agents

Read (10) Write / Execute (5) Destructive / Financial (2)
Critical Risk

The most dangerous Infinite Context Keeper tools

7 of Infinite Context Keeper's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

How to control Infinite Context Keeper

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

Deny destructive operations
{
  "delete_memory": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
{
  "project_create_milestone": {
    "limits": [
      {
        "counter": "project_create_milestone_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
{
  "get_context_usage": {
    "limits": [
      {
        "counter": "get_context_usage_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

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

  1. Create a free account and register Infinite Context Keeper — nothing to install.
  2. Add these rules — paste them, or build them visually. Tune the limits to your setup.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
ENFORCE POLICY ON INFINITE CONTEXT KEEPER →

Instant setup, no code required.

All 17 Infinite Context Keeper tools

READ 10 tools
Read get_context_usage MCP 호스트가 넘기는 used_tokens·대화 본문·tool 결과 문자열을 tiktoken으로 합산해 컨텍스트 사용량을 추정합니다. Read get_server_info 런타임 진단: 패키지·Node 버전, 해석된 data_dir, embedding_enabled, sqlite-vec 활성 여부, 임베딩 파이프라인 로드 여부 등. Read inject_relevant_memories semantic_search_memory와 동일 스코프로 검색 후 tiktoken 예산 내 마크다운 블록을 만듭니다. Read list_memories SQLite에 저장된 compaction 요약 등의 메타를 나열합니다. Read memory_search 시맨틱 메모리(semantic_memories) + 결정/지식 테이블 텍스트에 로컬 임베딩 코사인 랭킹을 합쳐 검색합니다. Read project_get_status Project Brain: 프로젝트 메타, 마일스톤·태스크, 최근 결정/지식, Unity 파일 인덱스 건수를 한 번에 조회합니다. project_id 생략 시 default_project_id. Read search_and_inject_memory 새 세션/compaction 직후 컨텍스트 상단 주입 블록을 반환합니다. Read semantic_search_memory 관련 메모리 청크를 반환합니다. sqlite-vec(vec0) KNN이 켜지면 DB 내 벡터 인덱스로 검색하고, 아니면 JS 코사인으로 폴백합니다. Read task_break_down Project Brain: 마일스톤을 세부 태스크로 나눕니다. tasks가 비어 있으면 마일스톤 정보와 함께 모델이 tasks 배열을 채워 재호출하도록 안내합니다. Read unity_scan_project Unity 프로젝트 루트(기본: process.cwd)를 스캔해 project_files 테이블을 갱신합니다. Assets가 있으면 그 하위 위주로 .cs 등 인덱싱.

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

Questions about Infinite Context Keeper

Can an AI agent delete data through the Infinite Context Keeper MCP server? +

Yes. The Infinite Context Keeper server exposes 2 destructive tools including delete_memory, reset_entire_database. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Infinite Context Keeper? +

The Infinite Context Keeper server has 4 write tools including project_create_milestone, project_resume, save_memory. 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 Infinite Context Keeper.

How many tools does the Infinite Context Keeper MCP server expose? +

17 tools across 4 categories: Destructive, Execute, Read, Write. 10 are read-only. 7 can modify, create, or delete data.

How do I enforce a policy on Infinite Context Keeper? +

Register the Infinite Context Keeper 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 Infinite Context Keeper tool call.

Deterministic rules across all 17 Infinite Context Keeper tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Instant setup, no code required.

17 Infinite Context Keeper tools catalogued and risk-classified — across an index of 43,000+ 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.