delete_alias

Delete an alias for a specific index.

Server Elasticsearch/OpenSearch MCP Server rbedoyag/elasticsearch-mcp-server
Category Destructive
Risk class Critical
Parameters 00 required

What delete_alias does on Elasticsearch/OpenSearch MCP Server

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

Why delete_alias needs a policy

Deleting an alias is an irreversible action that removes a named reference to an index. While less severe than deleting the underlying index itself, alias deletion can cause immediate operational failures for any clients or applications relying on that alias for queries or writes. This meets the Destructive category definition: actions that cannot be undone.

From the tool's definition Tool name is 'delete_alias' and description states 'Delete an alias'. The verb 'delete' is irreversible — removing an alias cannot be undone without manual recreation and may break client applications or queries depending on that alias.

Questions about delete_alias

What does the delete_alias tool do? +

Delete an alias for a specific index. It is categorised as a Destructive tool in the Elasticsearch/OpenSearch 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 delete_alias? +

Register the Elasticsearch/OpenSearch MCP Server MCP server in PolicyLayer and add a rule for delete_alias: 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 Elasticsearch/OpenSearch MCP Server. Nothing to install.

What risk level is delete_alias? +

delete_alias 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_alias? +

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

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

delete_alias is provided by the Elasticsearch/OpenSearch MCP Server MCP server (rbedoyag/elasticsearch-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.