MCP Server Policy
ELASTICSEARCH MCP POLICY
Enforce policies on every tool call to the Elasticsearch MCP Server. 5 tools listed, categorised, and ready for rules.
GET STARTED
Download this policy scaffold and add your rules. Intercept enforces them on every tool call before it reaches Elasticsearch.
# Download policy scaffold
curl -o elasticsearch.yaml https://raw.githubusercontent.com/policylayer/intercept/main/policies/elasticsearch.yaml
# Run with Intercept
intercept --policy elasticsearch.yaml -- npx -y @mcp-server-elasticsearch Server documentation: https://github.com/elastic/mcp-server-elasticsearch
READ TOOLS
4EXECUTE TOOLS
1POLICY YAML
This scaffold lists every tool with empty rules. Add conditions — rate limits, argument validation, deny rules — then deploy with Intercept.
version: "1"
description: "Policy for mcp-server-elasticsearch"
default: "allow"
tools:
list_indices:
rules: []
get_mappings:
rules: []
search:
rules: []
get_shards:
rules: []
esql:
rules: [] RELATED POLICIES
FREQUENTLY ASKED QUESTIONS
What tools does the Elasticsearch MCP server expose?
The Elasticsearch MCP Server exposes 5 tools across 2 categories: Read, Execute. Each tool can be individually controlled with Intercept policies.
How do I enforce policies on Elasticsearch?
Download the policy scaffold, add rules (rate limits, argument validation, deny rules), then run Intercept as a proxy in front of the Elasticsearch MCP server. Every tool call is evaluated against your YAML policy before execution.
Is the Elasticsearch policy free to use?
Yes. All Intercept policies are open source under the Apache 2.0 licence. Download, modify, and deploy without restrictions.
ENFORCE POLICIES ON ELASTICSEARCH
Open source. One binary. Zero dependencies.