enable_two_factor
Enable two-factor authentication for your account
This record as markdown: /tools/takashito-linode-mcp-server/enable-two-factor.md
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.
Why enable_two_factor is rated Medium
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
Attacks that exploit this kind of access
The rule that runs enable_two_factor safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Linode MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For enable_two_factor, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Linode MCP Server, apply this rule, and every enable_two_factor call is checked against it from then on.
Questions about enable_two_factor
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.
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.
enable_two_factor 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 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.
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.
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.
More on Linode MCP Server, and thousands of servers like it.
This server
Across the catalogue