deleteConsentWithId
Deletes the consent for the given Id.
This record as markdown: /tools/io-fusionauth-mcp-api/deleteconsentwithid.md
What deleteConsentWithId does on Fusionauth
AI agents call deleteConsentWithId to permanently remove resources in Fusionauth, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why deleteConsentWithId is rated Critical
This tool permanently removes consent records, which cannot be undone. Consent data is critical for compliance (GDPR, CCPA) and user trust. Unauthorized deletion could violate regulations, breach user privacy rights, and create legal liability. The high severity reflects the irreversible nature and compliance implications, though not critical since it affects individual consents rather than systemic infrastructure.
From the tool's definition Deletes the consent for the given Id - the verb 'Deletes' directly indicates irreversible removal of data without recovery mechanism.
Attacks that exploit this kind of access
The rule that runs deleteConsentWithId 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 deleteConsentWithId, this is the rule to start with:
deleteConsentWithId is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Fusionauth, apply this rule, and every deleteConsentWithId call is checked against it from then on.
Questions about deleteConsentWithId
Deletes the consent for the given Id. It is categorised as a Destructive tool in the Fusionauth MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Fusionauth MCP server in PolicyLayer and add a rule for deleteConsentWithId: 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.
deleteConsentWithId is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the deleteConsentWithId 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 deleteConsentWithId. 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.
deleteConsentWithId 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.
Across the catalogue