get_upgrade_results
AI agents call get_upgrade_results 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.
The tool name strongly indicates a query/retrieval operation that returns results of upgrades rather than triggering upgrades or modifying state. Confidence is moderate (0.60) due to empty description, but the consistent 'get_' prefix across all sibling tools and the pattern of the Wazuh server providing monitoring/analysis capabilities supports Read classification.
From the tool's definition Tool name 'get_upgrade_results' suggests retrieval of upgrade status/outcomes. No description provided, but follows the 'get_*' naming pattern consistent with sibling Read tools (get_active_configuration, get_agent_component_stats, get_agent_daemon_stats,…
Attacks that exploit this kind of access
get_upgrade_results. 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_upgrade_results: 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_upgrade_results 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_upgrade_results 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_upgrade_results. 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_upgrade_results 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 →