list_databases

List catalogs/databases for one backend.

SERVERMulti-DB MCP Server SOURCE1249zts/db-mcp-service

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/1249zts-db-mcp-service/list-databases.md

WHAT IT DOES

What list_databases does on Multi-DB MCP Server

AI agents call list_databases to retrieve information from Multi-DB MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_databases is rated Low

This tool queries database metadata (available databases/catalogs) without performing any write, execute, or destructive operations. It is a read-only information retrieval function with minimal risk. Severity is low because the blast radius of misuse is limited to information disclosure of database names, which are typically not sensitive enough to warrant higher severity in most contexts.

From the tool's definition Tool name 'list_databases' and description 'List catalogs/databases for one backend' indicate a retrieval operation with no modification or deletion of data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_databases safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Multi-DB MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_databases, this is the rule to start with:

list_databases Allowed

list_databases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_databases": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Multi-DB MCP Server, apply this rule, and every list_databases call is checked against it from then on.

FAQ

Questions about list_databases

What does the list_databases tool do? +

List catalogs/databases for one backend. It is categorised as a Read tool in the Multi-DB MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_databases? +

Register the Multi-DB MCP Server MCP server in PolicyLayer and add a rule for list_databases: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Multi-DB MCP Server. Nothing to install.

What risk level is list_databases? +

list_databases is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_databases? +

Yes. Add a rate_limit block to the list_databases rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block list_databases completely? +

Set action: deny in the PolicyLayer policy for list_databases. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides list_databases? +

list_databases is provided by the Multi-DB MCP Server MCP server (1249zts/db-mcp-service). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Multi-DB MCP Server, and thousands of servers like it.

This server

All 5 Multi-DB MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →