Get indexes for a specific table
AI agents call get_indexes to retrieve information from PostgreSQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves index metadata for a table, which is a read-only operation with no side effects. It returns informational schema data to help understand database structure, consistent with the server's stated purpose of allowing exploration of database schemas and metadata. The blast radius of misuse is minimal—an agent could learn about indexes but cannot modify data, execute queries, or cause data loss.
From the tool's definition Tool name 'get_indexes' and description 'Get indexes for a specific table' indicate retrieval of metadata about database indexes. No modification, deletion, or execution of arbitrary code is implied.
Attacks that exploit this kind of access
Get indexes for a specific table. 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 get_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.
get_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 get_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 get_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.
get_indexes is provided by the PostgreSQL MCP Server MCP server (sbfulfil/pg-mcp). 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 →