totp_disable
Disable two-factor authentication. Requires a current 6-digit authenticator code or one unused recovery code, in addition to the caller's authenticated session.
This record as markdown: /tools/io-github-kivanccakmak-yaver/totp-disable.md
What totp_disable does on Yaver
AI agents use totp_disable 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 or one unused recovery code |
Parameters from the server's own tool schema.
Why totp_disable is rated Medium
Modifies security credentials reversibly; high blast radius if authentication context spoofed.
From the tool's definition Disable two-factor authentication requires authenticator code or recovery code.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs totp_disable 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_disable, this is the rule to start with:
totp_disable 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_disable call is checked against it from then on.
Questions about totp_disable
Disable two-factor authentication. Requires a current 6-digit authenticator code or one unused recovery code, in addition to the caller's authenticated session. 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_disable 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_disable: 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_disable 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_disable 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_disable. 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_disable 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