check_wazuh

Check Wazuh security platform API reachability via GET /. Default port 55000 with HTTPS. Returns 401 when up (auth required but server is responding).

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

WHAT IT DOES

What check_wazuh does on Mcp Nettools

AI agents call check_wazuh 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_wazuh is rated Low

This is a read-only diagnostic check that queries the reachability status of a Wazuh API endpoint. It retrieves information about whether a service is responding without modifying state or executing code. The 401 response is simply an indicator that authentication is required, not that the tool performs any authenticated operations. Classification as Read is appropriate for a reachability/health check operation.

From the tool's definition Tool performs a GET request to check API reachability and returns server status (401 response indicates server is up). No data modification, deletion, or external command execution occurs. The description states it checks reachability via GET /.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

check_wazuh Allowed

check_wazuh 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_wazuh": {}
  }
}

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

FAQ

Questions about check_wazuh

What does the check_wazuh tool do? +

Check Wazuh security platform API reachability via GET /. Default port 55000 with HTTPS. Returns 401 when up (auth required but server is responding). 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_wazuh? +

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

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

Can I rate-limit check_wazuh? +

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

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

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