get_agent_packages
AI agents call get_agent_packages to retrieve information from Wazuh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Although the description is empty, the naming convention and context of sibling tools that are all retrieval operations ('get_') strongly indicate this is a read-only operation that queries or retrieves package information from a Wazuh agent. No side effects, modifications, deletions, or external operations are implied. Low severity due to typical low sensitivity of package listing data.
From the tool's definition Tool name 'get_agent_packages' follows the 'get_*' pattern used consistently across sibling tools (get_active_configuration, get_agent_component_stats, get_agent_daemon_stats, get_agent_hardware, get_agent_hotfixes, get_agent_key, get_agent_netaddr).
Attacks that exploit this kind of access
get_agent_packages. It is categorised as a Read tool in the Wazuh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wazuh MCP Server MCP server in PolicyLayer and add a rule for get_agent_packages: 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 Wazuh MCP Server. Nothing to install.
get_agent_packages is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_agent_packages 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.
Set action: deny in the PolicyLayer policy for get_agent_packages. 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.
get_agent_packages is provided by the Wazuh MCP Server MCP server (rayasatriatama/wazuh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →