⏳ Get list of pending approval requests.
AI agents call rbac_get_pending_approvals 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/lists pending approval requests with no side effects. It follows the Read pattern of querying existing data. The RBAC context indicates it operates within role-based access control, further supporting that this is an informational lookup. The blast radius of misuse is minimal—an attacker would only gain visibility into pending approvals, not the ability to approve, modify, or delete them.
From the tool's definition Tool name 'rbac_get_pending_approvals' and description 'Get list of pending approval requests' indicate a retrieval operation that queries approval data without modifying or executing anything.
Attacks that exploit this kind of access
⏳ Get list of pending approval requests. 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_pending_approvals: 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_pending_approvals 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_pending_approvals 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_pending_approvals. 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_pending_approvals 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 →