list_rbac_resources
AI agents call list_rbac_resources 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 follows the 'list_*' pattern typical of read-only operations that enumerate or retrieve data. RBAC resource listing is a query operation that retrieves access control information without side effects. The empty description reduces confidence slightly, but the naming convention and context among sibling tools (which include get_*, list_*, count_* — all read operations) confirm this is a read operation.
From the tool's definition Tool name 'list_rbac_resources' indicates a listing/retrieval operation. The 'list_' prefix strongly suggests querying role-based access control resources without modification. Description is empty, limiting certainty.
Attacks that exploit this kind of access
list_rbac_resources. 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 list_rbac_resources: 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.
list_rbac_resources 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 list_rbac_resources 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 list_rbac_resources. 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.
list_rbac_resources 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 →