start_unstake

Begin unstaking TWO (starts the vault cooldown; claim with claim_unstaked after it passes).

SERVERTwofold SOURCEtwofold-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/twofold-mcp/start-unstake.md

WHAT IT DOES

What start_unstake does on Twofold

AI agents invoke start_unstake to trigger actions in Twofold. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why start_unstake is rated High

start_unstake triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs start_unstake safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Twofold, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For start_unstake, this is the rule to start with:

start_unstake Rate-limited

start_unstake stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_unstake": {
      "limits": [
        {
          "counter": "start_unstake_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about start_unstake

What does the start_unstake tool do? +

Begin unstaking TWO (starts the vault cooldown; claim with claim_unstaked after it passes). It is categorised as a Execute tool in the Twofold MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on start_unstake? +

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

What risk level is start_unstake? +

start_unstake is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_unstake? +

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

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

start_unstake is provided by the Twofold MCP server (twofold-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Twofold, and thousands of servers like it.

This server

All 14 Twofold tools → High-risk tools on this server →

Across the catalogue

start_devtools_monitoring on Percepta MCP Server →team_manager_start_room on Team Manager MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →