Low Risk

list_tables

Get a list of all tables in the database

How to control list_tables ↓

What list_tables does on PostgreSQL Full Access MCP Server

AI agents call list_tables to retrieve information from PostgreSQL Full Access MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why list_tables needs a policy

This tool queries database structure and returns information only. It has no side effects, no data modification, and no irreversible actions. The blast radius of misuse is minimal—an attacker learns the schema but cannot alter or access table contents without additional tools. Severity is low because schema enumeration alone poses limited risk in most contexts.

From the tool's definition Tool name is 'list_tables' and description states 'Get a list of all tables in the database' — this retrieves metadata without modifying any data.

Documented attack patterns abuse exactly the kind of access list_tables gives an agent:

How to control list_tables

PolicyLayer is an MCP gateway — it sits between your AI agents and PostgreSQL Full Access MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_tables:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tables": {}
  }
}

list_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register PostgreSQL Full Access MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about list_tables

What does the list_tables tool do? +

Get a list of all tables in the database. It is categorised as a Read tool in the PostgreSQL Full Access MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tables? +

Register the PostgreSQL Full Access 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 Full Access MCP Server. Nothing to install.

What risk level is list_tables? +

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

Can I rate-limit list_tables? +

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.

How do I block list_tables completely? +

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.

What MCP server provides list_tables? +

list_tables is provided by the PostgreSQL Full Access MCP Server MCP server (syahiidkamil/mcp-postgres-full-access). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PostgreSQL Full Access MCP Server tool call.

Start from PostgreSQL Full Access MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

7 PostgreSQL Full Access MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.