Drop an index
AI agents call drop_index to permanently remove resources in PostgreSQL MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Dropping an index is an irreversible deletion of a database object. While not as severe as dropping a table or purging data, index removal can significantly degrade query performance and requires explicit recreation to restore. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone'.
From the tool's definition Tool name is 'drop_index' with description 'Drop an index'. The verb 'drop' is a SQL DDL operation that irreversibly removes database objects. This is a destructive operation that cannot be undone without recreation.
Attacks that exploit this kind of access
Drop an index. It is categorised as a Destructive tool in the PostgreSQL MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the PostgreSQL MCP Server MCP server in PolicyLayer and add a rule for drop_index: 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.
drop_index 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 drop_index 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 drop_index. 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.
drop_index is provided by the PostgreSQL MCP Server MCP server (reckersai/mcpg). 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 →