Medium Risk

enable_two_factor

Enable two-factor authentication for your account

How to control enable_two_factor ↓

What enable_two_factor does on Linode MCP Server

AI agents use enable_two_factor to create or update resources in Linode MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Linode MCP Server environment.

Medium Risk

Why enable_two_factor needs a policy

This tool modifies account security settings by enabling 2FA. It is a reversible write operation (2FA can be disabled), not destructive or financial. Misuse could lock out legitimate users or alter security posture, giving it medium severity.

From the tool's definition Enable two-factor authentication for your account

Documented attack patterns abuse exactly the kind of access enable_two_factor gives an agent:

How to control enable_two_factor

PolicyLayer is an MCP gateway — it sits between your AI agents and Linode MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for enable_two_factor:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "enable_two_factor": {
      "limits": [
        {
          "counter": "enable_two_factor_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Linode MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about enable_two_factor

What does the enable_two_factor tool do? +

Enable two-factor authentication for your account. It is categorised as a Write tool in the Linode MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on enable_two_factor? +

Register the Linode MCP Server MCP server in PolicyLayer and add a rule for enable_two_factor: 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 Linode MCP Server. Nothing to install.

What risk level is enable_two_factor? +

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

Can I rate-limit enable_two_factor? +

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

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

enable_two_factor is provided by the Linode MCP Server MCP server (takashito/linode-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Linode MCP Server tool call.

Start from Linode MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

416 Linode MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.