list_tables
List tables for the target database.
What list_tables does on Multi-DB MCP Server
AI agents call list_tables 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_tables is rated Low
This tool retrieves metadata about tables in a database without creating, modifying, or deleting any data. It is a read-only operation that returns information about the database schema. The severity is low because the blast radius of misuse is minimal—an AI agent listing tables cannot cause harm beyond information disclosure, which is typically low-risk in most database environments.
From the tool's definition Tool name is 'list_tables' and description states it 'List tables for the target database' — a query operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_tables 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_tables, this is the rule to start with:
list_tables 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_tables call is checked against it from then on.
Questions about list_tables
List tables for the target database. 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_tables: 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_tables 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_tables 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_tables. 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_tables 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