Low Risk

get_mapping

Get index mapping

How to control get_mapping ↓

What get_mapping does on OpenSearch MCP Server

AI agents call get_mapping to retrieve information from OpenSearch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_mapping needs a policy

The tool retrieves index mapping metadata from OpenSearch, which is a read-only query operation. It does not create, modify, delete, or execute any code. The blast radius is minimal; exposure would allow an attacker to learn the schema of indices but not access data, modify configurations, or trigger operations. Severity is low because mapping information is typically non-sensitive structural metadata.

From the tool's definition Tool name is 'get_mapping' and description states 'Get index mapping' — a retrieval operation with no modification or execution of code.

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

How to control get_mapping

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_mapping": {}
  }
}

get_mapping is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register OpenSearch 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.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_mapping

What does the get_mapping tool do? +

Get index mapping. It is categorised as a Read tool in the OpenSearch MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_mapping? +

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

What risk level is get_mapping? +

get_mapping is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_mapping? +

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

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

get_mapping is provided by the OpenSearch MCP Server MCP server (seohyunjun/opensearch-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 OpenSearch MCP Server tool call.

Start from OpenSearch 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.

14 OpenSearch 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.