get_list_rbac_actions
AI agents call get_list_rbac_actions 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 or lists RBAC actions available in the Wazuh system. It has no description, which moderately lowers confidence, but the 'get_list_' prefix is a strong signal of read-only retrieval with no side effects. RBAC action enumeration is a typical security audit or configuration query. No capability to modify, execute, or delete is evident from the name.
From the tool's definition Tool name 'get_list_rbac_actions' uses the 'get_list' pattern, indicating a query/retrieval operation. The 'rbac_actions' subject matter refers to listing role-based access control actions, which is informational.
Attacks that exploit this kind of access
get_list_rbac_actions. 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_list_rbac_actions: 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_list_rbac_actions 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_list_rbac_actions 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_list_rbac_actions. 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_list_rbac_actions 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 →