List all tables in a schema (PostgreSQL/MSSQL) or database (MySQL/SQLite)
AI agents call list_tables 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 tool only queries and returns metadata about database structure (table names). It has no side effects, does not modify data, and does not execute arbitrary operations. It is a read-only introspection tool, consistent with sibling tools like 'list_schemas', 'list_views', and 'describe_table'. The blast radius if misused is minimal—an AI agent could only enumerate available tables, which is informational only.
From the tool's definition Tool name 'list_tables' and description state it 'List all tables in a schema (PostgreSQL/MSSQL) or database (MySQL/SQLite)' — a pure retrieval operation with no modifications, deletions, or code execution.
Attacks that exploit this kind of access
List all tables in a schema (PostgreSQL/MSSQL) or database (MySQL/SQLite). 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_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 Database 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 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 →