theprotocol_disable2FASelf

DESTRUCTIVE: disable your own 2FA. Requires TOTP code.

SERVERTheProtocol — Sovereign AI Agent Platform SOURCEhttps://api.theprotocol.cloud/mcp/sse
Critical RISK CLASS
Category Destructive
Parameters 11 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cloud-theprotocol-registry/theprotocol-disable2faself.md

What theprotocol_disable2FASelf does on TheProtocol — Sovereign AI Agent Platform

AI agents call theprotocol_disable2FASelf to permanently remove resources in TheProtocol — Sovereign AI Agent Platform, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

ParameterTypeRequiredDescription
code string Yes

Parameters from the server's own tool schema.

Why theprotocol_disable2FASelf is rated Critical

The tool explicitly labels itself as DESTRUCTIVE and disables two-factor authentication, which is a security-critical irreversible action (until re-enabled) that removes an important security control. Misuse by an AI agent could expose accounts to unauthorized access, making severity high.

From the tool's definition DESTRUCTIVE: disable your own 2FA. Requires TOTP code.

Risk signalsAccepts freeform code/query input (code)

Questions about theprotocol_disable2FASelf

What does the theprotocol_disable2FASelf tool do? +

DESTRUCTIVE: disable your own 2FA. Requires TOTP code. It is categorised as a Destructive tool in the TheProtocol — Sovereign AI Agent Platform MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does theprotocol_disable2FASelf accept? +

theprotocol_disable2FASelf 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 theprotocol_disable2FASelf? +

Register the TheProtocol — Sovereign AI Agent Platform MCP server in PolicyLayer and add a rule for theprotocol_disable2FASelf: 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 TheProtocol — Sovereign AI Agent Platform. Nothing to install.

What risk level is theprotocol_disable2FASelf? +

theprotocol_disable2FASelf is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit theprotocol_disable2FASelf? +

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

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

theprotocol_disable2FASelf is provided by the TheProtocol — Sovereign AI Agent Platform MCP server (https://api.theprotocol.cloud/mcp/sse). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on TheProtocol — Sovereign AI Agent Platform, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of TheProtocol — Sovereign AI Agent Platform's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.