pg_duplicate_indexes
Find duplicate or overlapping indexes (same leading columns). Candidates for consolidation.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-duplicate-indexes.md
What pg_duplicate_indexes does on PostgreSQL MCP Server
AI agents call pg_duplicate_indexes 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_duplicate_indexes is rated Low
This tool performs read-only analysis of PostgreSQL indexes to identify consolidation candidates. It queries system catalogs and compares index structures but does not modify, delete, or execute any changes. The output is informational metadata intended to guide manual optimization decisions. This is a classic Read category tool with minimal blast radius if misused by an agent.
From the tool's definition Tool description states it 'Find[s] duplicate or overlapping indexes' — a query operation that retrieves and analyzes index metadata. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs pg_duplicate_indexes 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_duplicate_indexes, this is the rule to start with:
pg_duplicate_indexes 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_duplicate_indexes call is checked against it from then on.
Questions about pg_duplicate_indexes
Find duplicate or overlapping indexes (same leading columns). Candidates for consolidation. 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_duplicate_indexes: 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_duplicate_indexes 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_duplicate_indexes 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_duplicate_indexes. 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_duplicate_indexes 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