// SCAN REPORT

Db Oauth

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

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

Last updated: 3 Jul 2026

2 can modify or destroy data

3 read-only

5 tools total

Community server · catalogue entry verified 03/07/2026

How to control Db Oauth ↓

TOOL MAP

What Db Oauth exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Db Oauth tools

Execute · High query_database Although described as read-only, the tool executes arbitrary SQL queries against a database backend. Write · Medium disconnect Disconnecting from database connections and revoking access tokens modifies the authentication state but does not delete data or execute arbitrary operations.

2 of Db Oauth'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 Db Oauth

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

Rate limit write operations

{
  "disconnect": {
    "limits": [
      {
        "counter": "disconnect_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "connection_status": {
    "limits": [
      {
        "counter": "connection_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 Db Oauth — 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 OAUTH →

Instant setup, no code required.

FULL CATALOGUE

All 5 Db Oauth tools

EXECUTE 1 tools

Execute query_database Execute a read-only SQL query against one of the configured database connections.

WRITE 1 tools

Write disconnect Disconnect from all database connections. Revokes the current access token and

READ 3 tools

Read connection_status Show whether you Read list_connections List the database connections available in the current session. Returns the Read list_schema List tables or describe a specific table\

FAQ

Questions about Db Oauth

How do I prevent bulk modifications through Db Oauth? +

The Db Oauth server has 1 write tools including disconnect. 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 Oauth.

How many tools does the Db Oauth MCP server expose? +

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

How do I enforce a policy on Db Oauth? +

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

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

ENFORCE POLICY ON DB OAUTH →

Instant setup, no code required.

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

// WHERE THIS COMES FROM

These policies come from Db Oauth'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 →