clerk.delete_user_totp
Delete all TOTP authenticators for a Clerk user. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns the updated user object. Cost = 8 tokens.
This record as markdown: /tools/io-github-vee3io-vee3/clerk.delete-user-totp.md
What clerk.delete_user_totp does on Vee3
AI agents call clerk.delete_user_totp to permanently remove resources in Vee3, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
user_id | string | Yes | Clerk user id (user_...) to operate on. |
clerk_instance_id | object | — | Clerk instance id (ins_...) from clerk.get_connected_accounts. Omit to use the default connected account. |
Parameters from the server's own tool schema.
Why clerk.delete_user_totp is rated Critical
Irreversibly removes user's two-factor authentication, enabling account takeover.
From the tool's definition Delete all TOTP authenticators for a Clerk user.
Attacks that exploit this kind of access
The rule that runs clerk.delete_user_totp safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Vee3, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For clerk.delete_user_totp, this is the rule to start with:
clerk.delete_user_totp 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 Vee3, apply this rule, and every clerk.delete_user_totp call is checked against it from then on.
Questions about clerk.delete_user_totp
Delete all TOTP authenticators for a Clerk user. Call clerk.get_connected_accounts first. Pass clerk_instance_id to target a specific connection, or omit it to use the default account. Returns the updated user object. Cost = 8 tokens. It is categorised as a Destructive tool in the Vee3 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
clerk.delete_user_totp accepts 2 parameters: user_id, clerk_instance_id. Required: user_id. The full parameter table on this page comes from the server's own tool schema.
Register the Vee3 MCP server in PolicyLayer and add a rule for clerk.delete_user_totp: 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 Vee3. Nothing to install.
clerk.delete_user_totp 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 clerk.delete_user_totp 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 clerk.delete_user_totp. 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.
clerk.delete_user_totp is provided by the Vee3 MCP server (https://mcp.vee3.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vee3, and thousands of servers like it.
Across the catalogue