rbac_create_tenant · n8n Workflow Builder MCP: Risk & Policy

WHAT IT DOES

What rbac_create_tenant does on n8n Workflow Builder

AI agents use rbac_create_tenant 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.

WHY IT NEEDS A POLICY

Why rbac_create_tenant needs a policy

Creating a tenant is a reversible modification that establishes new multi-tenant boundaries and access control structures. While this is a Write operation (not Destructive, as tenant deletion would typically be available separately), the severity is high because uncontrolled tenant creation could compromise isolation boundaries, inflate costs, create orphaned resources, or enable privilege escalation across tenant…

From the tool's definition Tool name 'rbac_create_tenant' and description 'Create a new tenant for multi-tenant isolation' indicate creation of new organizational/security boundaries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rbac_create_tenant Rate-limited

rbac_create_tenant stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "rbac_create_tenant": {
      "limits": [
        {
          "counter": "rbac_create_tenant_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches n8n Workflow Builder, so you can run agents against it safely.

FAQ

Questions about rbac_create_tenant

What does the rbac_create_tenant tool do? +

🏢 Create a new tenant for multi-tenant isolation. 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.

How do I enforce a policy on rbac_create_tenant? +

Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for rbac_create_tenant: 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.

What risk level is rbac_create_tenant? +

rbac_create_tenant is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit rbac_create_tenant? +

Yes. Add a rate_limit block to the rbac_create_tenant 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.

How do I block rbac_create_tenant completely? +

Set action: deny in the PolicyLayer policy for rbac_create_tenant. 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.

What MCP server provides rbac_create_tenant? +

rbac_create_tenant 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.