totp_enable_begin
Start two-factor enrollment. Returns a base32 secret and an otpauth:// URL the user can scan into Microsoft Authenticator, Google Authenticator, 1Password, or any RFC 6238 TOTP app. After scanning, the user must confirm by running totp_enable_confirm with a 6-digit code from the app.
This record as markdown: /tools/io-github-kivanccakmak-yaver/totp-enable-begin.md
What totp_enable_begin does on Yaver
AI agents use totp_enable_begin 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.
Why totp_enable_begin is rated Medium
This tool creates/modifies account authentication configuration by initiating TOTP enrollment. It is reversible (enrollment can be cancelled or disabled later) and has no permanent destructive effects. The severity is medium because misconfiguration of 2FA could lock out legitimate users, but the operation itself is not irreversible and does not execute arbitrary code or move money.
From the tool's definition Tool description states it 'Start[s] two-factor enrollment' and 'Returns a base32 secret and an otpauth:// URL'. This initiates a reversible configuration change to the user's account security settings.
Attacks that exploit this kind of access
The rule that runs totp_enable_begin 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_begin, this is the rule to start with:
totp_enable_begin 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_begin call is checked against it from then on.
Questions about totp_enable_begin
Start two-factor enrollment. Returns a base32 secret and an otpauth:// URL the user can scan into Microsoft Authenticator, Google Authenticator, 1Password, or any RFC 6238 TOTP app. After scanning, the user must confirm by running totp_enable_confirm with a 6-digit code from the app. 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.
Register the Yaver MCP server in PolicyLayer and add a rule for totp_enable_begin: 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_begin 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_begin 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_begin. 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_begin 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