revokeRefreshTokenByIdWithId
Revokes a single refresh token by the unique Id. The unique Id is not sensitive as it cannot be used to obtain another JWT.
This record as markdown: /tools/io-fusionauth-mcp-api/revokerefreshtokenbyidwithid.md
What revokeRefreshTokenByIdWithId does on Fusionauth
AI agents call revokeRefreshTokenByIdWithId 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 revokeRefreshTokenByIdWithId is rated Critical
Revoking a refresh token is an irreversible action — once revoked, the token cannot be restored. This forces the affected user to re-authenticate. It fits the Destructive category as the revocation cannot be undone, though severity is medium since it affects only a single token and doesn't destroy account data.
From the tool's definition Revokes a single refresh token by the unique Id
Attacks that exploit this kind of access
The rule that runs revokeRefreshTokenByIdWithId 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 revokeRefreshTokenByIdWithId, this is the rule to start with:
revokeRefreshTokenByIdWithId 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 revokeRefreshTokenByIdWithId call is checked against it from then on.
Questions about revokeRefreshTokenByIdWithId
Revokes a single refresh token by the unique Id. The unique Id is not sensitive as it cannot be used to obtain another JWT. 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 revokeRefreshTokenByIdWithId: 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.
revokeRefreshTokenByIdWithId 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 revokeRefreshTokenByIdWithId 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 revokeRefreshTokenByIdWithId. 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.
revokeRefreshTokenByIdWithId 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