ATK Security Checks

Audit Wazuh custom rules

audit_wazuh_rules

Read-onlyIdempotent

Finds Wazuh custom rules that pass wazuh-analysisd -t but are dropped at load (load order across ruleset/rules and etc/rules, missing parents, duplicate or colliding ids). Input: list of {filename, xml}. Supported versions: 4.14.7, 4.14.9. Free: counts + 2 findings. Full report: pass api_key.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "files": "<files>"
    },
    "name": "audit_wazuh_rules"
  }
}

Input Schema

Name	Required	Description	Default
`files`	Yes	Custom rule files, each {"filename": "0094-local.xml", "xml": "<group>...</group>"}; filename exactly as in /var/ossec/etc/rules/, up to 20 files.
`api_key`	No	Optional key for the full report. Without it you get counts and 2 findings; the full report is also sold per call by x402 at POST https://atkvn.com/agent/v1/wazuh-audit.
`wazuh_version`	No	Wazuh manager version: 4.14.7 or 4.14.9.	4.14.9

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 22, 2026

TDQS

A3.9/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description adds the non-obvious behavioral facts: version gating (4.14.7/4.14.9), the free tier returns only counts plus 2 findings, and the full report requires an api_key. It doesn't describe error behavior or result structure, but the paywall and version constraints are genuinely useful disclosures beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the detection purpose, then input, versions, and paywall in compact sentences with no filler. The parenthetical failure-mode list is dense but earns its place; nothing needs to be cut.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the burden of return values and does state what the free tier returns (counts + 2 findings) and how to get the full report. It leaves out the structure/fields of findings and any error or rate-limit behavior, which keeps it short of fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so all three parameters are already documented in detail. The description restates the input shape ({filename, xml}) and the api_key/version constraints without adding format or semantic detail beyond the schema, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Finds Wazuh custom rules') plus the precise failure mode it detects (rules that pass wazuh-analysisd -t but are dropped at load, with load-order, missing-parent, and duplicate-id causes). This scope is clearly distinct from the sibling test_wazuh_rule, which implies testing a single rule rather than auditing a multi-file ruleset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the description makes clear it audits custom rule files against supported Wazuh versions, but never says when to prefer it over test_wazuh_rule or check_php2shell, nor states prerequisites or exclusions. An agent can infer the right context but gets no explicit routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All ATK Security Checks tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?