Get index usage statistics for a table or all tables in schema
AI agents call postgres_index_usage to retrieve information from Multi-Database MCP Server 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 (pg_stat_user_indexes or similar) to retrieve index performance metrics. It has no side effects, cannot modify data, and poses minimal risk even if misused by an AI agent. The only potential concern is information disclosure about database schema structure, which is typically low-severity.
From the tool's definition Tool name 'postgres_index_usage' combined with description 'Get index usage statistics for a table or all tables in schema' indicates retrieval of query performance metadata.
Attacks that exploit this kind of access
Get index usage statistics for a table or all tables in schema. It is categorised as a Read tool in the Multi-Database MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Multi-Database MCP Server MCP server in PolicyLayer and add a rule for postgres_index_usage: 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 Multi-Database MCP Server. Nothing to install.
postgres_index_usage 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 postgres_index_usage 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 postgres_index_usage. 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.
postgres_index_usage is provided by the Multi-Database MCP Server MCP server (nam088/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →