ℹ️ Get detailed information about a user.
AI agents call rbac_get_user_info 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 user information without side effects. It queries existing data about a user within n8n's role-based access control (RBAC) system. The 'Get' verb and informational purpose confirm it is a Read operation. Severity is low because unauthorized retrieval of user metadata carries limited blast radius compared to code execution or data destruction, though it could expose user details depending on scope.
From the tool's definition Tool name 'rbac_get_user_info' and description 'Get detailed information about a user' indicate a read-only retrieval operation with no modification or execution capability.
Attacks that exploit this kind of access
ℹ️ Get detailed information about a user. 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_user_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 n8n Workflow Builder. Nothing to install.
rbac_get_user_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 rbac_get_user_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 rbac_get_user_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.
rbac_get_user_info 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 →