list_enabled_databases
List enabled database targets: postgres / clickhouse / mysql.
This record as markdown: /tools/1249zts-db-mcp-service/list-enabled-databases.md
What list_enabled_databases does on Multi-DB MCP Server
AI agents call list_enabled_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.
Why list_enabled_databases is rated Low
This tool retrieves and queries configuration metadata without side effects. It does not modify, execute, or delete anything. It falls squarely into the Read category—safe informational access. Severity is low because exposure of which database systems are enabled poses minimal security risk on its own, though it could inform reconnaissance. Confidence is high because the name and description are unambiguous.
From the tool's definition Tool name 'list_enabled_databases' and description 'List enabled database targets' indicates a query/retrieval operation with no data modification. Returns only configuration metadata about which database systems are enabled.
Attacks that exploit this kind of access
The rule that runs list_enabled_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_enabled_databases, this is the rule to start with:
list_enabled_databases is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Multi-DB MCP Server, apply this rule, and every list_enabled_databases call is checked against it from then on.
Questions about list_enabled_databases
List enabled database targets: postgres / clickhouse / mysql. It is categorised as a Read tool in the Multi-DB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-DB MCP Server MCP server in PolicyLayer and add a rule for list_enabled_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.
list_enabled_databases is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_enabled_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.
Set action: deny in the PolicyLayer policy for list_enabled_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.
list_enabled_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.
More on Multi-DB MCP Server, and thousands of servers like it.
This server
Across the catalogue