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.

Single-target operation

Part of the Mcp Api MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@fusionauth/mcp-api Destructive Risk 4/5

// WHEN AI AGENTS USE THIS TOOL

AI agents may call revokeRefreshTokenByIdWithId to permanently remove or destroy resources in Mcp Api. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

// WHY ENFORCE A POLICY ON REVOKEREFRESHTOKENBYIDWITHID

Without a policy, an AI agent could call revokeRefreshTokenByIdWithId in a loop, permanently destroying resources in Mcp Api. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

// RECOMMENDED POLICY

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-fusionauth-mcp-api.yaml

tools:
  revokeRefreshTokenByIdWithId:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Mcp Api policy for all 310 tools.

// DETAILS

Tool Name revokeRefreshTokenByIdWithId

Category Destructive

MCP Server Mcp Api MCP Server

Risk Level Critical

// MORE MCP API TOOLS

Destructive cancelActionWithId Destructive changePasswordWithId Destructive deleteAPIKeyWithId Destructive deleteApplicationRoleWithId Destructive deleteApplicationWithId Destructive deleteConnectorWithId Destructive deleteConsentWithId Destructive deleteEmailTemplateWithId

View all 310 tools →

// RELATED READING

// FAQ

What does the revokeRefreshTokenByIdWithId tool do? +

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 Mcp Api MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on revokeRefreshTokenByIdWithId? +

Add a rule in your Intercept YAML policy under the tools section for revokeRefreshTokenByIdWithId. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Api MCP server.

What risk level is revokeRefreshTokenByIdWithId? +

revokeRefreshTokenByIdWithId is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit revokeRefreshTokenByIdWithId? +

Yes. Add a rate_limit block to the revokeRefreshTokenByIdWithId rule in your Intercept 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.

How do I block revokeRefreshTokenByIdWithId completely? +

Set action: deny in the Intercept 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.

What MCP server provides revokeRefreshTokenByIdWithId? +

revokeRefreshTokenByIdWithId is provided by the Mcp Api MCP server (@fusionauth/mcp-api). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

revokeRefreshTokenByIdWithId

Enforce policies on Mcp Api