totp_enable_confirm
Confirm two-factor enrollment with a 6-digit code from the authenticator app, enabling 2FA for the account. Returns 8 one-time recovery codes — show them to the user once and instruct them to save somewhere safe.
This record as markdown: /tools/io-github-kivanccakmak-yaver/totp-enable-confirm.md
What totp_enable_confirm does on Yaver
AI agents use totp_enable_confirm to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | Current 6-digit TOTP code from the authenticator |
Parameters from the server's own tool schema.
Why totp_enable_confirm is rated Medium
This tool creates or modifies account security settings (two-factor authentication) and generates recovery codes, which are write operations with side effects. It does not delete data (so not Destructive), does not execute arbitrary code (so not Execute), and does not move money (so not Financial).
From the tool's definition Tool modifies account security state by 'enabling 2FA for the account' and returns 'recovery codes' that must be saved. These are persistent, irreversible changes to authentication configuration.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs totp_enable_confirm safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For totp_enable_confirm, this is the rule to start with:
totp_enable_confirm stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every totp_enable_confirm call is checked against it from then on.
Questions about totp_enable_confirm
Confirm two-factor enrollment with a 6-digit code from the authenticator app, enabling 2FA for the account. Returns 8 one-time recovery codes — show them to the user once and instruct them to save somewhere safe. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
totp_enable_confirm accepts 1 parameter: code. Required: code. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for totp_enable_confirm: 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 Yaver. Nothing to install.
totp_enable_confirm is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the totp_enable_confirm 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 totp_enable_confirm. 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.
totp_enable_confirm is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue