// SCAN REPORT

23 Open Chat Reviewer

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

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

Last updated: 7 Oct 2026

1 can modify or destroy data

4 read-only

5 tools total

Community server · catalogue entry checked 07/10/2026

How to control 23 Open Chat Reviewer ↓

TOOL MAP

What 23 Open Chat Reviewer exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous 23 Open Chat Reviewer tools

Write · Medium archive_status archive_status

1 of 23 Open Chat Reviewer'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 23 Open Chat Reviewer

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

Rate limit write operations

{
  "archive_status": {
    "limits": [
      {
        "counter": "archive_status_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_conversations": {
    "limits": [
      {
        "counter": "find_conversations_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 23 Open Chat Reviewer — 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 23 OPEN CHAT REVIEWER →

Instant setup, no code required.

FULL CATALOGUE

All 5 23 Open Chat Reviewer tools

WRITE 1 tools

Write archive_status archive_status

READ 4 tools

Read find_conversations find_conversations Read get_conversation_trace get_conversation_trace Read get_recent_work get_recent_work Read search_archive search_archive

FAQ

Questions about 23 Open Chat Reviewer

How do I prevent bulk modifications through 23 Open Chat Reviewer? +

The 23 Open Chat Reviewer server has 1 write tools including archive_status. 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 23 Open Chat Reviewer.

How many tools does the 23 Open Chat Reviewer MCP server expose? +

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

How do I enforce a policy on 23 Open Chat Reviewer? +

Register the 23 Open Chat Reviewer 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 23 Open Chat Reviewer tool call.

Deterministic rules across all 5 23 Open Chat Reviewer tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON 23 OPEN CHAT REVIEWER →

Instant setup, no code required.

5 23 Open Chat Reviewer tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from 23 Open Chat Reviewer'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 →