devnet_status

Report the local L1s and whether the local network is running.

SERVERAvalanche SOURCE@avakit/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-avakit-avalanche/devnet-status.md

WHAT IT DOES

What devnet_status does on Avalanche

AI agents call devnet_status to retrieve information from Avalanche without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why devnet_status is rated Low

Tool only queries and reports network status without modifying or executing state changes.

From the tool's definition Report the local L1s and whether the local network is running.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

devnet_status Allowed

devnet_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "devnet_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about devnet_status

What does the devnet_status tool do? +

Report the local L1s and whether the local network is running. It is categorised as a Read tool in the Avalanche MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on devnet_status? +

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

devnet_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit devnet_status? +

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

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

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

Across the catalogue

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →