totp_enable_confirm · Yaver MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

Parameter	Type	Required	Description
`code`	string	Yes	Current 6-digit TOTP code from the authenticator

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why totp_enable_confirm needs a policy

An AI agent can call totp_enable_confirm faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

Risk signalsAccepts freeform code/query input (code)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

totp_enable_confirm Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "totp_enable_confirm": {
      "limits": [
        {
          "counter": "totp_enable_confirm_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Yaver, so you can run agents against it safely.

FAQ

Questions about totp_enable_confirm

What does the totp_enable_confirm tool do? +

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.

What parameters does totp_enable_confirm accept? +

totp_enable_confirm accepts 1 parameter: code. Required: code. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on totp_enable_confirm? +

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.

What risk level is totp_enable_confirm? +

totp_enable_confirm is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit totp_enable_confirm? +

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.

How do I block totp_enable_confirm completely? +

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.

What MCP server provides totp_enable_confirm? +

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.