get-all-tables

THE RISK

Low Risk

Why get-all-tables needs a policy

This tool retrieves metadata about existing tables (schema exploration) with no side effects or data modification. The server is explicitly described as 'read-only SQL execution' and 'table exploration', and this tool fits that pattern.

From the tool's definition Tool name 'get-all-tables' and description 'Execute SQL queries to get all tables in the database' indicate a retrieval operation that lists database schema metadata without modifying data.

Risk signalsBulk/mass operation — affects multiple targets

Documented attack patterns abuse exactly the kind of access get-all-tables gives an agent:

POLICY

How to control get-all-tables

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

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-all-tables": {}
  }
}

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

Create a free account and register PostgreSQL MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get-all-tables

What does the get-all-tables tool do? +

Execute SQL queries to get all tables in the database. 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 get-all-tables? +

Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for get-all-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 get-all-tables? +

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

Can I rate-limit get-all-tables? +

Yes. Add a rate_limit block to the get-all-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 get-all-tables completely? +

Set action: deny in the PolicyLayer policy for get-all-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 get-all-tables? +

get-all-tables is provided by the PostgreSQL MCP Server MCP server (martymarkenson/postgres-connector-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PostgreSQL MCP Server tool call.

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

CHECK YOUR STACK →