🔒 Get RBAC and security status report.
AI agents call rbac_get_status to retrieve information from n8n Workflow Builder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports on existing RBAC (Role-Based Access Control) and security status. It performs no mutations, executions, or destructive operations. The blast radius of misuse is minimal — an attacker gains visibility into access controls but cannot modify them or execute actions. This is a read-only information disclosure risk at worst.
From the tool's definition Tool name contains 'get' and description states 'Get RBAC and security status report' — explicit retrieval of configuration/status data with no modification or execution.
Attacks that exploit this kind of access
🔒 Get RBAC and security status report. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for rbac_get_status: 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 n8n Workflow Builder. Nothing to install.
rbac_get_status 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 rbac_get_status 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 rbac_get_status. 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.
rbac_get_status is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). 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 →