AI agents call get_settings 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.
This tool retrieves configuration data about OpenSearch indices without altering state. It is purely informational—getting settings is a safe read operation comparable to querying metadata. No side effects, no modifications, no destructive capability.
From the tool's definition Tool name 'get_settings' and description 'Get index settings' indicate a retrieval operation with no modification capability.
Documented attack patterns abuse exactly the kind of access get_settings gives an agent:
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_settings:
{
"version": "1",
"default": "deny",
"tools": {
"get_settings": {}
}
}get_settings is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get index settings. It is categorised as a Read tool in the OpenSearch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenSearch MCP Server MCP server in PolicyLayer and add a rule for get_settings: 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.
get_settings 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_settings 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_settings. 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_settings 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.
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.