devnet_launch_l1

Create a single custom Subnet-EVM L1 and deploy it locally. Returns the exit code and log tail; read the chain

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-launch-l1.md

WHAT IT DOES

What devnet_launch_l1 does on Avalanche

AI agents invoke devnet_launch_l1 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_launch_l1 is rated High

Launches and deploys blockchain infrastructure locally; triggers external operations with broad side effects.

From the tool's definition Create a single custom Subnet-EVM L1 and deploy it locally

Attacks that exploit this kind of access

RECOMMENDED RULE

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

devnet_launch_l1 Rate-limited

devnet_launch_l1 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_launch_l1": {
      "limits": [
        {
          "counter": "devnet_launch_l1_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_launch_l1 call is checked against it from then on.

FAQ

Questions about devnet_launch_l1

What does the devnet_launch_l1 tool do? +

Create a single custom Subnet-EVM L1 and deploy it locally. Returns the exit code and log tail; read the chain. 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_launch_l1? +

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

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

Can I rate-limit devnet_launch_l1? +

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

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

devnet_launch_l1 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 →