pg_index_recommendations
Suggest missing indexes based on table statistics or query analysis. When sql is provided and HypoPG is installed, creates hypothetical indexes to measure potential performance improvement.
This record as markdown: /tools/io-github-neverinfamous-postgres-mcp/pg-index-recommendations.md
What pg_index_recommendations does on PostgreSQL MCP Server
AI agents call pg_index_recommendations 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_index_recommendations is rated Low
This tool analyzes existing data and query patterns to provide recommendations, and creates temporary hypothetical indexes for analysis purposes only. It does not create, modify, or delete actual database indexes or other persistent objects. The operation has no side effects on the production database state, making it a Read category tool with low severity.
From the tool's definition Tool description states it 'suggest[s] missing indexes based on table statistics or query analysis' and 'creates hypothetical indexes to measure potential performance improvement.' The use of 'hypothetical indexes' and performance measurement indicates…
Attacks that exploit this kind of access
The rule that runs pg_index_recommendations 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_index_recommendations, this is the rule to start with:
pg_index_recommendations 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_index_recommendations call is checked against it from then on.
Questions about pg_index_recommendations
Suggest missing indexes based on table statistics or query analysis. When sql is provided and HypoPG is installed, creates hypothetical indexes to measure potential performance improvement. 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_index_recommendations: 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_index_recommendations 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_index_recommendations 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_index_recommendations. 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_index_recommendations 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