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.

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

Questions about pg_index_recommendations

What does the pg_index_recommendations tool do? +

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.

How do I enforce a policy on pg_index_recommendations? +

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.

What risk level is pg_index_recommendations? +

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

Can I rate-limit pg_index_recommendations? +

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.

How do I block pg_index_recommendations completely? +

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.

What MCP server provides pg_index_recommendations? +

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.

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