devnet_start

Start the local Avalanche network.

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-start.md

WHAT IT DOES

What devnet_start does on Avalanche

AI agents invoke devnet_start 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_start is rated High

Initiates a network service whose side effects depend on system state and configuration.

From the tool's definition Start the local Avalanche network. Triggers external operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs devnet_start 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_start, this is the rule to start with:

devnet_start Rate-limited

devnet_start 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_start": {
      "limits": [
        {
          "counter": "devnet_start_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_start call is checked against it from then on.

FAQ

Questions about devnet_start

What does the devnet_start tool do? +

Start the local Avalanche network. 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_start? +

Register the Avalanche MCP server in PolicyLayer and add a rule for devnet_start: 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_start? +

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

Can I rate-limit devnet_start? +

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

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

devnet_start 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

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

Guides

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