// SCAN REPORT

Db

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

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

Last updated: 12 Jun 2026

17 can modify or destroy data

17 read-only

34 tools total

Community server · catalogue entry verified 12/06/2026

How to control Db ↓

TOOL MAP

What Db exposes to your agents

Read (17) Write / Execute (11) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Db tools

Destructive · High mongodb_delete_one This tool permanently removes data without possibility of recovery (barring backups). Destructive · High mysql_delete MySQL DELETE is a destructive operation that permanently removes records from a database. Destructive · High redis_del Deleting a Redis key is an irreversible operation — once deleted, the key and its associated data are gone unless a backup exists. Execute · Critical set_security_mode This tool changes the security enforcement mode of the entire MCP server.

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

POLICY

How to control Db

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

Deny destructive operations

{
  "mongodb_delete_one": {
    "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

{
  "mongodb_connect": {
    "limits": [
      {
        "counter": "mongodb_connect_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_security_mode": {
    "limits": [
      {
        "counter": "get_security_mode_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 Db — 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 DB →

Free to start. No card required.

FULL CATALOGUE

All 34 Db tools

DESTRUCTIVE 3 tools

Destructive mongodb_delete_one 删除 MongoDB 集合中的单个文档 Destructive mysql_delete 执行 MySQL DELETE 删除操作。若服务启动时已预配置 MySQL，会直接使用默认连接。 Destructive redis_del 删除 Redis 键

EXECUTE 2 tools

Execute mysql_query 执行 MySQL SQL 语句（支持 SELECT、INSERT、UPDATE、DELETE 等所有 SQL 操作）。如果服务启动时已预配置 MySQL，本工具会直接复用默认连接，无需先调用 mysql_connect。 Execute set_security_mode 设置安全模式：read_only（只读模式）、restricted（限制模式）、full_access（完全开发模式）

WRITE 9 tools

Write mongodb_connect 连接到 MongoDB 数据库 Write mongodb_insert_many 向 MongoDB 集合插入多个文档 Write mongodb_insert_one 向 MongoDB 集合插入单个文档 Write mongodb_update_one 更新 MongoDB 集合中的单个文档 Write mysql_connect 连接到 MySQL 数据库（支持连接池）。仅在服务启动时未预配置 MySQL，或你需要覆盖当前默认连接时使用。 Write mysql_insert 执行 MySQL INSERT 插入操作。若服务启动时已预配置 MySQL，会直接使用默认连接。 Write mysql_update 执行 MySQL UPDATE 更新操作。若服务启动时已预配置 MySQL，会直接使用默认连接。 Write redis_connect 连接到 Redis 数据库 Write redis_set 设置 Redis 键的值

READ 17 tools

Read get_security_mode 获取当前安全模式 Read mongodb_count 统计 MongoDB 集合中匹配的文档数量 Read mongodb_find 在 MongoDB 集合中查找文档 Read mongodb_find_one 在 MongoDB 集合中查找单个文档 Read mongodb_list_collections 列出 MongoDB 数据库中的所有集合 Read mysql_connection_status 获取当前 MySQL 默认连接状态。查询前可先调用此工具判断服务启动时的预配置连接是否已可用；若已连接，直接使用 mysql_query 等工具，无需先调用 mysql_connect。 Read mysql_pool_status 获取当前 MySQL 连接池状态（如果使用连接池）。若服务启动时已预配置并启用了连接池，也会返回默认连接的状态。 Read redis_get 从 Redis 获取键的值 Read server_runtime_status 获取服务运行时状态，包括并发限制、队列、响应限制、超时和连接状态。查询数据库前，可先查看 connections.mysql / redis / mongodb 判断启动时默认连接是否已可用。 Read redis_auto_prefix_memory_usage 自动按键名前缀聚合当前 Redis 数据库的内存占用 Read redis_hget 获取 Redis 哈希字段的值 Read redis_hgetall 获取 Redis 哈希的所有字段和值 Read redis_keys 使用 SCAN 查找匹配模式的 Redis 键，避免 KEYS 阻塞实例 Read redis_memory_usage 获取 Redis 键的内存占用字节数 Read redis_memory_usage_by_prefixes 按多个 Redis 键前缀模式分组统计总内存占用 Read redis_top_memory_keys 扫描当前 Redis 数据库并返回内存占用最高的键 Read redis_type 获取 Redis 键的数据类型

OTHER 3 tools

Other mongodb_disconnect 断开 MongoDB 数据库连接 Other mysql_disconnect 断开当前 MySQL 数据库连接，包括启动时已建立的默认连接。 Other redis_disconnect 断开 Redis 数据库连接

EXPLORE

Related servers

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

FAQ

Questions about Db

Can an AI agent delete data through the Db MCP server? +

Yes. The Db server exposes 3 destructive tools including mongodb_delete_one, mysql_delete, redis_del. 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 Db? +

The Db server has 9 write tools including mongodb_connect, mongodb_insert_many, mongodb_insert_one. 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 Db.

How many tools does the Db MCP server expose? +

34 tools across 3 categories: Destructive, Read, Write. 17 are read-only. 17 can modify, create, or delete data.

How do I enforce a policy on Db? +

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

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

ENFORCE POLICY ON DB →

Free to start. No card required.

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