List all tables, views, and materialized views in a schema with estimated row counts and sizes. Defaults to the
AI agents call listTables to retrieve information from Postgresql without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema metadata (table names, views, row counts, sizes) without creating, modifying, deleting, or executing any operations. It produces no side effects and poses minimal risk even if invoked by a confused AI agent. Classified as Read with low severity.
From the tool's definition Tool name 'listTables' and description 'List all tables, views, and materialized views in a schema' indicates retrieval/query operation with no modification. Action is read-only metadata inspection.
Attacks that exploit this kind of access
List all tables, views, and materialized views in a schema with estimated row counts and sizes. Defaults to the. It is categorised as a Read tool in the Postgresql MCP Server, which means it retrieves data without modifying state.
Register the Postgresql MCP server in PolicyLayer and add a rule for listTables: 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. Nothing to install.
listTables 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 listTables 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 listTables. 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.
listTables is provided by the Postgresql MCP server (vnikhilbuddhavarapu/postgresql-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 →