get_rbac_resources
AI agents call get_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.
This tool retrieves RBAC resource information from the Wazuh platform for inspection. It has no side effects—it does not modify, delete, or execute operations. It fits the 'Read' category as a data retrieval function. Confidence is reduced slightly (0.75) due to the empty description, which prevents full confirmation of scope, but the naming pattern and context strongly suggest a read-only operation.
From the tool's definition Tool name 'get_rbac_resources' follows the 'get_*' pattern consistent with sibling tools (get_active_configuration, get_agent_component_stats, get_agent_hardware, etc.) which are all read operations.
Attacks that exploit this kind of access
get_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 get_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.
get_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 get_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 get_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.
get_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 →