Identify tables with high sequential scans that might need indexes.
AI agents call PostgreSQL_seqscan_heavy_tables to retrieve information from Postgres without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries PostgreSQL system catalogs and statistics to detect performance issues (sequential scans). It is a diagnostic Read operation with no side effects. The blast radius is minimal—worst case, an AI agent receives performance analysis recommendations that are informational only. The tool does not execute arbitrary code, modify data structures, or trigger external systems.
From the tool's definition Tool name contains 'Identify' and description states 'Identify tables with high sequential scans' — a diagnostic query operation that retrieves and analyzes database metadata without modifying data.
Documented attack patterns abuse exactly the kind of access PostgreSQL_seqscan_heavy_tables gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Postgres, and nothing reaches the server without passing your rules. This is the rule we recommend for PostgreSQL_seqscan_heavy_tables:
{
"version": "1",
"default": "deny",
"tools": {
"PostgreSQL_seqscan_heavy_tables": {}
}
}PostgreSQL_seqscan_heavy_tables is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Identify tables with high sequential scans that might need indexes. It is categorised as a Read tool in the Postgres MCP Server, which means it retrieves data without modifying state.
Register the Postgres MCP server in PolicyLayer and add a rule for PostgreSQL_seqscan_heavy_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 Postgres. Nothing to install.
PostgreSQL_seqscan_heavy_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 PostgreSQL_seqscan_heavy_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 PostgreSQL_seqscan_heavy_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.
PostgreSQL_seqscan_heavy_tables is provided by the Postgres MCP server (mukul975/postgres-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Postgres, 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.
239 Postgres tools catalogued and risk-classified — across an index of 43,000+ MCP servers.