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.

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-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.

Questions about pg_seq_scan_tables

What does the pg_seq_scan_tables tool do? +

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.

How do I enforce a policy on pg_seq_scan_tables? +

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.

What risk level is pg_seq_scan_tables? +

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

Can I rate-limit pg_seq_scan_tables? +

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.

How do I block pg_seq_scan_tables completely? +

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.

What MCP server provides pg_seq_scan_tables? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of PostgreSQL MCP Server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.