check_kibana

Check Kibana (Elastic Stack UI) reachability via GET /api/status. Default port 5601. Returns overall status color (green/yellow/red) from the health response.

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-kibana.md

WHAT IT DOES

What check_kibana does on Mcp Nettools

AI agents call check_kibana 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_kibana is rated Low

This is a read-only health check that queries Kibana's status endpoint and returns diagnostic information. It has no side effects, does not execute code or commands, does not modify data, and does not move money. The GET request and status retrieval are characteristic of Read-category operations.

From the tool's definition Tool performs a GET request to /api/status endpoint to retrieve reachability and health status; described as 'check' operation that 'returns' status information with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_kibana 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_kibana, this is the rule to start with:

check_kibana Allowed

check_kibana 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_kibana": {}
  }
}

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_kibana call is checked against it from then on.

FAQ

Questions about check_kibana

What does the check_kibana tool do? +

Check Kibana (Elastic Stack UI) reachability via GET /api/status. Default port 5601. Returns overall status color (green/yellow/red) from the health response. 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_kibana? +

Register the Mcp Nettools MCP server in PolicyLayer and add a rule for check_kibana: 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_kibana? +

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

Can I rate-limit check_kibana? +

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

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

check_kibana 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 →