deleteOAuthScopeWithId
Hard deletes a custom OAuth scope. OAuth workflows that are still requesting the deleted OAuth scope may fail depending on the application
This record as markdown: /tools/io-fusionauth-mcp-api/deleteoauthscopewithid.md
What deleteOAuthScopeWithId does on Fusionauth
AI agents call deleteOAuthScopeWithId 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 deleteOAuthScopeWithId is rated Critical
This tool permanently removes OAuth scope configuration data. The deletion is irreversible and has downstream consequences—existing OAuth workflows depending on the deleted scope will fail.
From the tool's definition Tool name contains 'delete' and description states 'Hard deletes a custom OAuth scope' with irreversible consequences ('OAuth workflows that are still requesting the deleted OAuth scope may fail').
Attacks that exploit this kind of access
The rule that runs deleteOAuthScopeWithId 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 deleteOAuthScopeWithId, this is the rule to start with:
deleteOAuthScopeWithId 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 deleteOAuthScopeWithId call is checked against it from then on.
Questions about deleteOAuthScopeWithId
Hard deletes a custom OAuth scope. OAuth workflows that are still requesting the deleted OAuth scope may fail depending on the application. 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 deleteOAuthScopeWithId: 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.
deleteOAuthScopeWithId 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 deleteOAuthScopeWithId 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 deleteOAuthScopeWithId. 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.
deleteOAuthScopeWithId 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