devnet_spin_up

Create two local Avalanche L1s with Interchain Messaging and a relayer, and deploy them locally. Idempotent. Takes a few minutes.

SERVERAvalanche SOURCE@avakit/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/dev-avakit-avalanche/devnet-spin-up.md

WHAT IT DOES

What devnet_spin_up does on Avalanche

AI agents invoke devnet_spin_up to trigger actions in Avalanche. 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 devnet_spin_up is rated High

Launches and deploys blockchain infrastructure locally with irreversible network state changes and relayer setup.

From the tool's definition Create two local Avalanche L1s, deploy them locally

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs devnet_spin_up safely

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

devnet_spin_up Rate-limited

devnet_spin_up 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": {
    "devnet_spin_up": {
      "limits": [
        {
          "counter": "devnet_spin_up_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 Avalanche, apply this rule, and every devnet_spin_up call is checked against it from then on.

FAQ

Questions about devnet_spin_up

What does the devnet_spin_up tool do? +

Create two local Avalanche L1s with Interchain Messaging and a relayer, and deploy them locally. Idempotent. Takes a few minutes. It is categorised as a Execute tool in the Avalanche MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on devnet_spin_up? +

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

What risk level is devnet_spin_up? +

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

Can I rate-limit devnet_spin_up? +

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

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

devnet_spin_up is provided by the Avalanche MCP server (@avakit/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Avalanche, and thousands of servers like it.

This server

All 16 Avalanche tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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