get_roles_info
AI agents call get_roles_info 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.
Based on naming convention consistent with other retrieval tools on the Wazuh MCP server, this tool retrieves role information from the Wazuh security platform without modifying, deleting, or executing any operations. The lack of descriptive text slightly reduces confidence, but the function name and context strongly indicate a read-only query operation.
From the tool's definition Tool name 'get_roles_info' indicates a retrieval operation. The description is empty, but the pattern matches sibling tools like 'get_agent_component_stats', 'get_agent_daemon_stats', 'get_agent_hardware', 'get_agent_hotfixes', 'get_agent_key', and…
Attacks that exploit this kind of access
get_roles_info. 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_roles_info: 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_roles_info 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_roles_info 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_roles_info. 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_roles_info 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 →