Get field mappings for a specific Elasticsearch index
AI agents call get_mappings to retrieve information from Custom Elasticsearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves structural information (field mappings) from an Elasticsearch index. It is a non-destructive read operation with no side effects. The blast radius of misuse is minimal — an attacker could discover the schema of sensitive data but cannot access the data itself, modify it, or execute operations. Confidence is high because the name and description unambiguously indicate a read-only query.
From the tool's definition Tool name is 'get_mappings' and description states 'Get field mappings for a specific Elasticsearch index' — a pure query operation that retrieves schema metadata without modifying data.
Attacks that exploit this kind of access
Get field mappings for a specific Elasticsearch index. It is categorised as a Read tool in the Custom Elasticsearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Custom Elasticsearch MCP Server MCP server in PolicyLayer and add a rule for get_mappings: 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 Custom Elasticsearch MCP Server. Nothing to install.
get_mappings is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_mappings 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 get_mappings. 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.
get_mappings is provided by the Custom Elasticsearch MCP Server MCP server (m0-ar/custom-elasticsearch-mcp-server). 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 →