check_opensearch

SERVERMcp Nettools SOURCEaaronckj/mcp-nettools

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aaronckj-mcp-nettools/check-opensearch.md

WHAT IT DOES

What check_opensearch does on Mcp Nettools

AI agents call check_opensearch to retrieve information from Mcp Nettools without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_opensearch is rated Low

This tool retrieves diagnostic information about an OpenSearch/Elasticsearch cluster's health and status. It uses the GET HTTP method on a standard read-only health endpoint, which cannot modify, delete, or execute arbitrary operations. The blast radius of misuse is minimal—an attacker would only gain visibility into cluster status information.

From the tool's definition Tool performs 'Check OpenSearch cluster health via GET /_cluster/health' which is a read-only health status query returning 'cluster name, status, node counts, and shard stats.' GET requests are inherently read operations with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_opensearch safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Nettools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_opensearch, this is the rule to start with:

check_opensearch Allowed

check_opensearch is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_opensearch": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Nettools, apply this rule, and every check_opensearch call is checked against it from then on.

FAQ

Questions about check_opensearch

What does the check_opensearch tool do? +

Check OpenSearch (or Elasticsearch-compatible) cluster health via GET /_cluster/health. Returns cluster name, status (green/yellow/red), node counts, and shard stats. Port 9200 = default HTTP, 9300 = transport. It is categorised as a Read tool in the Mcp Nettools MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_opensearch? +

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

What risk level is check_opensearch? +

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

Can I rate-limit check_opensearch? +

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

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

check_opensearch is provided by the Mcp Nettools MCP server (aaronckj/mcp-nettools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcp Nettools, and thousands of servers like it.

This server

All 235 Mcp Nettools tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →