# icm_state

Report each L1

Agent View of the PolicyLayer registry record for `icm_state`. HTML page: https://policylayer.com/tools/dev-avakit-avalanche/icm-state

## Facts

- Tool: `icm_state`
- Server: Avalanche (`@avakit/mcp`) — https://policylayer.com/tools/dev-avakit-avalanche.md
- Install: `npx -y @avakit/mcp`
- Homepage: https://github.com/mericcintosun/AvaKit
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "icm_state",
    "arguments": {}
  }
}
```

## Why icm_state is rated Low

Tool reports state information about L1s, a read-only operation.

From the tool's own definition: "Report each L1"

## Use case

AI agents call icm_state 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Avalanche:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "icm_state": {}
  }
}
```

## Other tools on Avalanche (15)

- `deploy_contract` — Execute — https://policylayer.com/tools/dev-avakit-avalanche/deploy-contract.md
- `devnet_launch_l1` — Execute — https://policylayer.com/tools/dev-avakit-avalanche/devnet-launch-l1.md
- `devnet_spin_up` — Execute — https://policylayer.com/tools/dev-avakit-avalanche/devnet-spin-up.md
- `devnet_start` — Execute — https://policylayer.com/tools/dev-avakit-avalanche/devnet-start.md
- `devnet_stop` — Execute — https://policylayer.com/tools/dev-avakit-avalanche/devnet-stop.md
- `icm_deploy_messengers` — Execute — https://policylayer.com/tools/dev-avakit-avalanche/icm-deploy-messengers.md
- `icm_send` — Execute — https://policylayer.com/tools/dev-avakit-avalanche/icm-send.md
- `avalanche_env` — Read — https://policylayer.com/tools/dev-avakit-avalanche/avalanche-env.md
- `data_lookup` — Read — https://policylayer.com/tools/dev-avakit-avalanche/data-lookup.md
- `devnet_status` — Read — https://policylayer.com/tools/dev-avakit-avalanche/devnet-status.md
- `estimate_gas` — Read — https://policylayer.com/tools/dev-avakit-avalanche/estimate-gas.md
- `get_context` — Read — https://policylayer.com/tools/dev-avakit-avalanche/get-context.md
- `list_templates` — Read — https://policylayer.com/tools/dev-avakit-avalanche/list-templates.md
- `read_chain` — Read — https://policylayer.com/tools/dev-avakit-avalanche/read-chain.md
- `scaffold_app` — Write — https://policylayer.com/tools/dev-avakit-avalanche/scaffold-app.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-avakit-avalanche · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-avakit-avalanche