delete_index_metadata

THE RISK

Critical Risk

Why delete_index_metadata needs a policy

Deleting metadata for an Elasticsearch index cannot be undone and may render the index unusable or cause loss of critical documentation about its schema and configuration. While not as severe as deleting the index itself, this causes permanent loss of structured information that cannot be reconstructed automatically. Destructive category applies because the action is irreversible and eliminates data.

From the tool's definition Tool name contains 'delete' and description states 'Delete metadata documentation' — both indicate irreversible removal of data without recovery mechanism.

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

POLICY

How to control delete_index_metadata

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_index_metadata"
  ]
}

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

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

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Agent Knowledge MCP tools

Destructive delete_document Delete a document from Elasticsearch index by document ID Destructive delete_index Delete an Elasticsearch index and all its documents permanently Destructive reset_config Reset config.json to defaults from config.default.json (manual reset - overwrites current Execute reload_config Reload configuration from config.json file and reinitialize all components with updated se Execute server_upgrade Upgrade this MCP server when installed via uvx with automatic configuration backup and res Execute setup_elasticsearch Auto-setup Elasticsearch using Docker with optional Kibana and force recreate options Write batch_index_directory Batch index all documents from a directory into Elasticsearch with AI-enhanced metadata ge Write index_document Index a document into Elasticsearch with smart duplicate prevention and intelligent docume

All 27 Agent Knowledge MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Agent Knowledge MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete_index_metadata

What does the delete_index_metadata tool do? +

Delete metadata documentation for an Elasticsearch index. It is categorised as a Destructive tool in the Agent Knowledge MCP 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 delete_index_metadata? +

Register the Agent Knowledge MCP server in PolicyLayer and add a rule for delete_index_metadata: 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 Agent Knowledge MCP. Nothing to install.

What risk level is delete_index_metadata? +

delete_index_metadata 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 delete_index_metadata? +

Yes. Add a rate_limit block to the delete_index_metadata 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 delete_index_metadata completely? +

Set action: deny in the PolicyLayer policy for delete_index_metadata. 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 delete_index_metadata? +

delete_index_metadata is provided by the Agent Knowledge MCP server (itshare4u/agentknowledgemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Agent Knowledge MCP tool call.

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

CHECK YOUR STACK →