wazuh-mcp

get_agent_ports

List open network ports on a Wazuh agent to identify active services and potential security exposures.

Instructions

List open network ports on a Wazuh agent

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": {
      "agent_id": "<agent_id>"
    },
    "name": "get_agent_ports"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum number of items to return (1-500)
`offset`	No	Pagination offset
`agent_id`	Yes	Agent identifier (e.g., '001')

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv1.1.0Jun 23, 2026
- removedInput schema / $schema
```
Removed value: -"http://json-schema.org/draft-07/schema#"
```
- addedInput schema / properties / agent_id / maxLength
```
Added value: +32
```
- addedInput schema / properties / agent_id / minLength
```
Added value: +1
```
- addedInput schema / properties / agent_id / pattern
```
Added value: +"^\\d+$"
```
- changedInput schema / properties / limit / description
```
Previous value: -"Maximum number of ports to return (1-500)"New value: +"Maximum number of items to return (1-500)"
```
- changedInput schema / properties / offset / maximum
```
Previous value: -9007199254740991New value: +100000
```
AddedMay 6, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description bears the full burden. It states a read operation (list), which is adequate, but lacks details on permissions, rate limits, or agent status requirements. Minimal but not deceptive.

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

Conciseness5/5

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

The description is a single sentence with no redundant information. Every word contributes to the purpose.

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

Completeness3/5

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

Given the tool's simplicity (3 parameters, no output schema, no annotations), the description conveys the core functionality but omits behavioral details like pagination or result format. Adequate for a straightforward list operation.

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?

The input schema provides 100% coverage with descriptions for agent_id, limit, and offset. The description adds no new meaning beyond what the schema already documents, so baseline score of 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?

The description clearly states 'List open network ports on a Wazuh agent', using a specific verb and resource. It distinguishes itself from sibling tools like get_agent_network (network interfaces) and get_agent_processes (processes).

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?

No explicit guidance on when to use this tool versus alternatives. The purpose is implied by the name and description, but there are no mentioned exclusions or context about when not to use it.

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