Critical Risk →

drop_index

Remove field(s) from a query index

How to control drop_index ↓

What drop_index does on Codehooks Io MCP Server

AI agents call drop_index to permanently remove resources in Codehooks Io MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why drop_index needs a policy

Dropping an index is an irreversible operation that cannot be undone without recreating it. While not deleting data itself, it destroys a database structure that cannot be recovered. An AI agent misusing this tool could degrade query performance or cause operational failures.

From the tool's definition Tool name 'drop_index' combined with description 'Remove field(s) from a query index' indicates irreversible deletion of database index structures. The verb 'drop' is a standard destructive database operation.

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

How to control drop_index

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

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "drop_index"
  ]
}

drop_index disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Codehooks Io MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about drop_index

What does the drop_index tool do? +

Remove field(s) from a query index. It is categorised as a Destructive tool in the Codehooks Io MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on drop_index? +

Register the Codehooks Io 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 Codehooks Io MCP Server. Nothing to install.

What risk level is drop_index? +

drop_index is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit drop_index? +

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.

How do I block drop_index completely? +

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.

What MCP server provides drop_index? +

drop_index is provided by the Codehooks Io MCP Server MCP server (restdb/codehooks-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 Codehooks Io MCP Server tool call.

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

Free to start. No card required.

20 Codehooks Io MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.