totp_status

Show whether two-factor authentication is enabled for the signed-in Yaver user. 2FA is optional and gates only session issuance — in-flight QUIC/relay traffic is never affected.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/totp-status.md

WHAT IT DOES

What totp_status does on Yaver

AI agents call totp_status to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why totp_status is rated Low

This tool only queries and displays the current 2FA status for the authenticated user. It has no side effects, does not execute code, does not modify state, and does not access sensitive data beyond the user's own authentication configuration. The blast radius of misuse is minimal — an agent learning that 2FA is enabled or disabled does not grant unauthorized access or enable further compromise.

From the tool's definition Tool description states it 'Show[s] whether two-factor authentication is enabled' — a read-only query operation that retrieves authentication status without modifying any data or triggering actions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs totp_status 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_status, this is the rule to start with:

totp_status Allowed

totp_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "totp_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every totp_status call is checked against it from then on.

FAQ

Questions about totp_status

What does the totp_status tool do? +

Show whether two-factor authentication is enabled for the signed-in Yaver user. 2FA is optional and gates only session issuance — in-flight QUIC/relay traffic is never affected. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on totp_status? +

Register the Yaver MCP server in PolicyLayer and add a rule for totp_status: 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_status? +

totp_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit totp_status? +

Yes. Add a rate_limit block to the totp_status 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_status completely? +

Set action: deny in the PolicyLayer policy for totp_status. 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_status? +

totp_status 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →