pg_seq_scan_tables
Find tables with high sequential scan counts (potential missing indexes). Default minScans=10; use higher values (e.g., 100+) for production databases.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-seq-scan-tables.md
What pg_seq_scan_tables does on PostgreSQL MCP Server
AI agents call pg_seq_scan_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 pg_seq_scan_tables is rated Low
This tool performs a read-only diagnostic query against PostgreSQL to identify tables with sequential scan patterns. It queries system statistics (likely pg_stat_user_tables or similar) to report findings, with no side effects, data modification, or destructive operations. The default parameter guidance (minScans=10) is for filtering results, not for mutation.
From the tool's definition Tool name 'pg_seq_scan_tables' and description 'Find tables with high sequential scan counts' indicate a query operation that retrieves diagnostic information about table scans without modifying any data.
Attacks that exploit this kind of access
The rule that runs pg_seq_scan_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_seq_scan_tables, this is the rule to start with:
pg_seq_scan_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 pg_seq_scan_tables call is checked against it from then on.
Questions about pg_seq_scan_tables
Find tables with high sequential scan counts (potential missing indexes). Default minScans=10; use higher values (e.g., 100+) for production databases. 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 pg_seq_scan_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.
pg_seq_scan_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 pg_seq_scan_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 pg_seq_scan_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.
pg_seq_scan_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.
More on PostgreSQL MCP Server, and thousands of servers like it.
This server
Across the catalogue