// SCAN REPORT

0CompactMem

8 tools. 3 can modify or destroy data without limits.

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

Last updated: 3 Jul 2026

3 can modify or destroy data

5 read-only

8 tools total

Community server · catalogue entry verified 03/07/2026

How to control 0CompactMem ↓

TOOL MAP

What 0CompactMem exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous 0CompactMem tools

Write · Medium memory_write The name 'memory_write' clearly indicates a write operation. Write · Medium pin_memory The tool name 'pin_memory' strongly suggests it pins memory entries (likely setting mlock/pinned flags on records in the SQLite store) to prevent eviction. Write · Medium unpin_memory This tool modifies the pinned state of a memory chunk, making it eligible for eviction.

3 of 0CompactMem's 8 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control 0CompactMem

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

Rate limit write operations

{
  "memory_write": {
    "limits": [
      {
        "counter": "memory_write_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "list_pinned": {
    "limits": [
      {
        "counter": "list_pinned_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 0CompactMem — 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 0COMPACTMEM →

Instant setup, no code required.

FULL CATALOGUE

All 8 0CompactMem tools

WRITE 3 tools

Write memory_write memory_write Write pin_memory pin_memory Write unpin_memory 解除 chunk 在当前项目中的 pin，允许被自动淘汰。

READ 5 tools

Read list_pinned 列出当前项目中所有 pinned chunks。 Read memory_applied memory_applied Read memory_hook_health Hook 系统健康检查 — 查看最近 N 小时内哪些 hook 在触发、哪些静默失败。 Read memory_lookup memory_lookup Read memory_stats 查询 AIOS 知识库的统计信息（chunk 数量、类型分布、近期活跃度）。

FAQ

Questions about 0CompactMem

How do I prevent bulk modifications through 0CompactMem? +

The 0CompactMem server has 3 write tools including memory_write, pin_memory, unpin_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 0CompactMem.

How many tools does the 0CompactMem MCP server expose? +

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

How do I enforce a policy on 0CompactMem? +

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

Deterministic rules across all 8 0CompactMem tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON 0COMPACTMEM →

Instant setup, no code required.

8 0CompactMem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.