// SCAN REPORT

MCP Atlas

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

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

Last updated: 30 Jun 2026

5 can modify or destroy data

1 read-only

6 tools total

Community server · catalogue entry verified 30/06/2026

How to control MCP Atlas ↓

TOOL MAP

What MCP Atlas exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous MCP Atlas tools

Execute · Critical migrate-apply Applying migrations executes DDL/DML statements against a database. Write · High migrate-diff migrate-diff generates new migration files, which are reversible modifications to database schemas and version control artifacts. Write · Medium migrate-new This tool creates a new migration file, which is a reversible write operation. Write · Medium migrate-lint Run analysis on migration directory to detect issues

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

POLICY

How to control MCP Atlas

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

Rate limit write operations

{
  "migrate-diff": {
    "limits": [
      {
        "counter": "migrate-diff_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "migrate-status": {
    "limits": [
      {
        "counter": "migrate-status_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 MCP Atlas — 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 MCP ATLAS →

Instant setup, no code required.

FULL CATALOGUE

All 6 MCP Atlas tools

EXECUTE 1 tools

Execute migrate-apply Apply pending migration files to a database

WRITE 4 tools

Write migrate-diff Generate a new migration file by comparing current state to desired schema Write migrate-lint Run analysis on migration directory to detect issues Write migrate-new Create a new empty migration file in the migration directory Write migrate-validate Validate migration directory integrity and consistency

READ 1 tools

Read migrate-status Report current migration status of a database

FAQ

Questions about MCP Atlas

How do I prevent bulk modifications through MCP Atlas? +

The MCP Atlas server has 4 write tools including migrate-diff, migrate-lint, migrate-new. 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 MCP Atlas.

How many tools does the MCP Atlas MCP server expose? +

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

How do I enforce a policy on MCP Atlas? +

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

Deterministic rules across all 6 MCP Atlas tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MCP ATLAS →

Instant setup, no code required.

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