get_active_configuration
AI agents call get_active_configuration 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.
This tool retrieves configuration data without modifying it, classifying it as Read. Severity is medium rather than low because configuration data in a security platform could be sensitive and might reveal attack surface or security posture if disclosed to an unauthorized AI agent. Confidence is 0.7 rather than higher because the description is empty, requiring inference from the tool name and sibling context.
From the tool's definition Tool name 'get_active_configuration' indicates a retrieval operation with no modification. Sibling tools like 'get_agent_component_stats', 'get_agent_hardware', 'get_agent_hotfixes', 'get_agent_netaddr', and 'get_agent_netiface' are all Read operations that…
Attacks that exploit this kind of access
get_active_configuration. 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_active_configuration: 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_active_configuration 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_active_configuration 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_active_configuration. 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_active_configuration 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 →