List all databases available on the server
AI agents call list_databases to retrieve information from Database MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward read operation that queries metadata about available databases. It has no capacity to modify data, execute code, delete resources, or incur financial obligations. The blast radius of misuse is minimal—an AI agent could only learn what databases exist, which is low-risk information disclosure. Confidence is high given the clear, unambiguous name and description.
From the tool's definition Tool name 'list_databases' and description 'List all databases available on the server' indicate a retrieval operation with no side effects. It merely enumerates available databases without modifying or executing anything.
Attacks that exploit this kind of access
List all databases available on the server. It is categorised as a Read tool in the Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Database 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 Database MCP Server. Nothing to install.
list_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_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_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_databases is provided by the Database MCP Server MCP server (zeaozhang/database-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →