Drop an existing index. By default drops it CONCURRENTLY (non-blocking). Cannot drop primary key or unique constraint indexes — use ALTER TABLE for those.
AI agents call dropIndex to permanently remove resources in Postgresql — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Dropping an index is a destructive operation that irreversibly removes database metadata and index data. While less critical than dropping a table, it can degrade query performance if done incorrectly and requires recreation to undo. This fits the Destructive category (actions that cannot be undone) rather than Write (reversible modifications).
From the tool's definition Tool name 'dropIndex' and description 'Drop an existing index' — the verb 'drop' in SQL is irreversible deletion.
Attacks that exploit this kind of access
Drop an existing index. By default drops it CONCURRENTLY (non-blocking). Cannot drop primary key or unique constraint indexes — use ALTER TABLE for those. It is categorised as a Destructive tool in the Postgresql MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Postgresql MCP server in PolicyLayer and add a rule for dropIndex: 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. Nothing to install.
dropIndex is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the dropIndex 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 dropIndex. 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.
dropIndex is provided by the Postgresql MCP server (vnikhilbuddhavarapu/postgresql-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 →