createTenant
Creates a tenant. You can optionally specify an Id for the tenant, if not provided one will be generated.
This record as markdown: /tools/io-fusionauth-mcp-api/createtenant.md
What createTenant does on Fusionauth
AI agents use createTenant to create or update resources in Fusionauth, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Fusionauth environment.
Why createTenant is rated Medium
Creating a tenant is a write operation that persistently adds a new entity to the system. It is reversible (a tenant can be deleted), so it does not qualify as Destructive. However, in a multi-tenant identity/authentication system like FusionAuth, creating a tenant is a significant action with potentially broad blast radius: a new tenant represents a new isolated security boundary, namespace, and billing entity.
From the tool's definition Tool description states 'Creates a tenant' — this is a create operation that generates a new organizational entity in FusionAuth. The optional Id parameter allows customization of the created resource.
Attacks that exploit this kind of access
The rule that runs createTenant safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fusionauth, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For createTenant, this is the rule to start with:
createTenant 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Fusionauth, apply this rule, and every createTenant call is checked against it from then on.
Questions about createTenant
Creates a tenant. You can optionally specify an Id for the tenant, if not provided one will be generated. It is categorised as a Write tool in the Fusionauth MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Fusionauth MCP server in PolicyLayer and add a rule for createTenant: 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 Fusionauth. Nothing to install.
createTenant 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 createTenant 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 createTenant. 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.
createTenant is provided by the Fusionauth MCP server (@fusionauth/mcp-api). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Fusionauth, and thousands of servers like it.
This server
Across the catalogue