📝 Create an approval request for a critical operation.
AI agents use rbac_create_approval_request to create or update resources in n8n Workflow Builder — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your n8n Workflow Builder environment.
This tool creates approval request records for critical operations—a reversible write operation that establishes new governance data. While it doesn't execute workflows or delete data, it modifies system state by creating approval objects. Severity is high because misuse could create unauthorized approval trails or bypass intended governance controls.
From the tool's definition Tool name contains 'create' and description states 'Create an approval request', indicating data creation. The context of 'critical operation' and 'approval request' suggests this modifies workflow state by creating audit/governance records.
Attacks that exploit this kind of access
📝 Create an approval request for a critical operation. It is categorised as a Write tool in the n8n Workflow Builder MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for rbac_create_approval_request: 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_create_approval_request is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rbac_create_approval_request 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_create_approval_request. 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_create_approval_request 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 →