createIdentityProvider
Creates an identity provider. You can optionally specify an Id for the identity provider, if not provided one will be generated.
This record as markdown: /tools/io-fusionauth-mcp-api/createidentityprovider.md
What createIdentityProvider does on Fusionauth
AI agents use createIdentityProvider 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 createIdentityProvider is rated Medium
Creating an identity provider is a write operation that modifies system configuration and authentication infrastructure. While reversible (not Destructive), it can have significant security implications since identity providers control authentication flows and user access.
From the tool's definition Tool description states 'Creates an identity provider' - a direct create operation that modifies FusionAuth configuration by adding a new identity provider resource. This is a reversible write operation (can be deleted), not a read-only query.
Attacks that exploit this kind of access
The rule that runs createIdentityProvider 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 createIdentityProvider, this is the rule to start with:
createIdentityProvider 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 createIdentityProvider call is checked against it from then on.
Questions about createIdentityProvider
Creates an identity provider. You can optionally specify an Id for the identity provider, 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 createIdentityProvider: 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.
createIdentityProvider 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 createIdentityProvider 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 createIdentityProvider. 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.
createIdentityProvider 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