// SCAN REPORT

MCP Universal DB Client

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

1 destructive tool with no built-in limits. Policy required.

Last updated: 4 Jul 2026

4 can modify or destroy data

2 read-only

6 tools total

Community server · catalogue entry verified 04/07/2026

How to control MCP Universal DB Client ↓

TOOL MAP

What MCP Universal DB Client exposes to your agents

Read (2) Write / Execute (3) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous MCP Universal DB Client tools

Destructive · Critical query_write This tool explicitly supports DELETE queries (irreversible data removal) alongside INSERT and UPDATE. Write · Medium disconnect_all Disconnecting all active database connections modifies system state by terminating running connections, which is a write-class operation. Write · Medium connect_database Connecting to a database creates a new resource and modifies the connection pool state. Write · Medium disconnect_database Disconnecting a database connection is a write operation because it changes the state of the system (connection pool state) reversibly.

4 of MCP Universal DB Client'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 Universal DB Client

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

Deny destructive operations

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

{
  "connect_database": {
    "limits": [
      {
        "counter": "connect_database_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "list_connections": {
    "limits": [
      {
        "counter": "list_connections_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 Universal DB Client — 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 UNIVERSAL DB CLIENT →

Instant setup, no code required.

FULL CATALOGUE

All 6 MCP Universal DB Client tools

DESTRUCTIVE 1 tools

Destructive query_write Run INSERT, UPDATE, DELETE and other destructive SQL queries on the connected database. Use with caution as th

WRITE 3 tools

Write connect_database Connect to a database using connection string Write disconnect_all Disconnect all active database connections Write disconnect_database Disconnect from a database using connection ID

READ 2 tools

Read list_connections List all active database connections Read query_read Run SELECT and other read-only SQL queries on the connected database. This tool only accepts non-destructive q

FAQ

Questions about MCP Universal DB Client

Can an AI agent delete data through the MCP Universal DB Client MCP server? +

Yes. The MCP Universal DB Client server exposes 1 destructive tools including query_write. 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 MCP Universal DB Client? +

The MCP Universal DB Client server has 3 write tools including connect_database, disconnect_all, disconnect_database. 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 Universal DB Client.

How many tools does the MCP Universal DB Client MCP server expose? +

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

How do I enforce a policy on MCP Universal DB Client? +

Register the MCP Universal DB Client 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 Universal DB Client tool call.

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

ENFORCE POLICY ON MCP UNIVERSAL DB CLIENT →

Instant setup, no code required.

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