createConsent
Creates a user consent type. You can optionally specify an Id for the consent type, if not provided one will be generated.
This record as markdown: /tools/io-fusionauth-mcp-api/createconsent.md
What createConsent does on Fusionauth
AI agents use createConsent 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 createConsent is rated Medium
The tool creates new consent type records in FusionAuth, which is a write operation. While consent management is important for compliance and user data governance, the action is reversible (consent types can be deleted or updated).
From the tool's definition Tool name is 'createConsent' and description states 'Creates a user consent type.' This is a creation operation that modifies data (adds a new consent type record) in a reversible manner.
Attacks that exploit this kind of access
The rule that runs createConsent 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 createConsent, this is the rule to start with:
createConsent 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 createConsent call is checked against it from then on.
Questions about createConsent
Creates a user consent type. You can optionally specify an Id for the consent type, 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 createConsent: 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.
createConsent 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 createConsent 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 createConsent. 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.
createConsent 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