get_indexes

THE RISK

Low Risk

Why get_indexes needs a policy

This tool queries database metadata about indexes and returns that information without any side effects or capability to alter data or schema. It is a read-only schema inspection operation with minimal risk if misused by an AI agent.

From the tool's definition get_indexes retrieves index information from a table with no modification capability. The tool is grouped with other schema inspection tools like get_columns, get_foreign_keys, get_schema_names, and get_tables.

Documented attack patterns abuse exactly the kind of access get_indexes gives an agent:

POLICY

How to control get_indexes

PolicyLayer is an MCP gateway — it sits between your AI agents and Pgsql, and nothing reaches the server without passing your rules. This is the rule we recommend for get_indexes:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_indexes": {}
  }
}

get_indexes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Pgsql — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Pgsql tools

Destructive run_ddl_query Run a raw DDL SQL query, like CREATE, ALTER, DROP, etc. Destructive run_dml_query Run a raw DML query, like INSERT, UPDATE, DELETE, etc. Execute run_dcl_query Run a raw DCL SQL query, like GRANT, REVOKE, etc. Read run_dql_query Run a raw DQL SQL query, like SELECT, SHOW, DESCRIBE, EXPLAIN, etc. Read get_columns Get all columns in a table. Read get_foreign_keys Get foreign keys in a table. Read get_schema_names Get all schema names. Read get_tables Get all tables in a schema.

All 9 Pgsql tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_indexes

What does the get_indexes tool do? +

Get all indexes in a table. It is categorised as a Read tool in the Pgsql MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_indexes? +

Register the Pgsql 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 Pgsql. Nothing to install.

What risk level is get_indexes? +

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

Can I rate-limit get_indexes? +

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.

How do I block get_indexes completely? +

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.

What MCP server provides get_indexes? +

get_indexes is provided by the Pgsql MCP server (twn39/pgsql-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Pgsql tool call.

Start from Pgsql, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →