pg_list_tables

List all tables, views, and materialized views with metadata. Use limit to restrict results.

SERVERPostgreSQL MCP Server SOURCE@neverinfamous/postgres-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-list-tables.md

WHAT IT DOES

What pg_list_tables does on PostgreSQL MCP Server

AI agents call pg_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.

RISK

Why pg_list_tables is rated Low

This tool retrieves database schema metadata without creating, modifying, deleting, or executing any operations. It has minimal blast radius—an AI agent misusing it could only over-retrieve metadata, which has no destructive side effects. Classified as Read with low severity.

From the tool's definition Tool description states 'List all tables, views, and materialized views with metadata' — a retrieval operation with no modification or execution capability. The 'limit' parameter further confirms it is a simple query/list function with read-only semantics.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs pg_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 pg_list_tables, this is the rule to start with:

pg_list_tables Allowed

pg_list_tables is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pg_list_tables": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect PostgreSQL MCP Server, apply this rule, and every pg_list_tables call is checked against it from then on.

FAQ

Questions about pg_list_tables

What does the pg_list_tables tool do? +

List all tables, views, and materialized views with metadata. Use limit to restrict results. It is categorised as a Read tool in the PostgreSQL MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on pg_list_tables? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for pg_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.

What risk level is pg_list_tables? +

pg_list_tables is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit pg_list_tables? +

Yes. Add a rate_limit block to the pg_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.

How do I block pg_list_tables completely? +

Set action: deny in the PolicyLayer policy for pg_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.

What MCP server provides pg_list_tables? +

pg_list_tables is provided by the PostgreSQL MCP Server MCP server (@neverinfamous/postgres-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

What pg_list_tables does on PostgreSQL MCP Server

Why pg_list_tables is rated Low

The rule that runs pg_list_tables safely

Questions about pg_list_tables

More on PostgreSQL MCP Server, and thousands of servers like it.