This record as markdown: /tools/io-fusionauth-mcp-api/createuserconsent.md
What createUserConsent does on Fusionauth
AI agents use createUserConsent 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 createUserConsent is rated Medium
This tool creates new data (user consent records) in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or move money. The severity is medium because creating user consent records could affect user preferences and permissions, but the blast radius is limited to consent data modification without cascading destructive effects.
From the tool's definition Tool name is 'createUserConsent' and description states it 'Creates a single User consent' — a direct create operation that modifies user data by recording consent preferences.
Attacks that exploit this kind of access
The rule that runs createUserConsent 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 createUserConsent, this is the rule to start with:
createUserConsent 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 createUserConsent call is checked against it from then on.
Questions about createUserConsent
Creates a single User consent. 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 createUserConsent: 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.
createUserConsent 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 createUserConsent 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 createUserConsent. 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.
createUserConsent 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