list_tables
List all tables in the current PostgreSQL database.
This record as markdown: /tools/aadarshjain-postgres-mcp-server/list-tables.md
What list_tables does on PostgreSQL MCP Server
AI agents call list_tables to retrieve information from PostgreSQL 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
The tool retrieves schema metadata (table names) from the database without side effects, modification, or execution of arbitrary operations. This is a standard Read operation. Severity is low because listing tables exposes minimal sensitive information compared to reading table contents, and has no blast radius if misused by an AI agent.
From the tool's definition Tool name is 'list_tables' and description states 'List all tables in the current PostgreSQL database.' This is a retrieval operation with no data modification or code execution.
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 PostgreSQL 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 PostgreSQL MCP Server, apply this rule, and every list_tables call is checked against it from then on.
Questions about list_tables
List all tables in the current PostgreSQL database. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PostgreSQL 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 PostgreSQL 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 PostgreSQL MCP Server MCP server (aadarshjain/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on PostgreSQL MCP Server, and thousands of servers like it.
This server
Across the catalogue