# scaffold_app

Create a new Avalanche dapp from a template (minimal, nft-mint, token-gated-app, erc20-token, icm-messenger, eerc-token, l1-launch, token-bridge). Wraps create-avalanche-app. Returns the created files and next steps.

Agent View of the PolicyLayer registry record for `scaffold_app`. HTML page: https://policylayer.com/tools/dev-avakit-avalanche/scaffold-app

## Facts

- Tool: `scaffold_app`
- 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: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

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

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

## Why scaffold_app is rated Medium

Generates new application files and project structure; reversible through deletion but alters local environment.

From the tool's own definition: "Create a new Avalanche dapp from a template, wraps create-avalanche-app, returns created files."

## Use case

AI agents use scaffold_app to create or update resources in Avalanche, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Avalanche environment.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "scaffold_app": {
      "limits": [
        {
          "counter": "scaffold_app_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## 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
- `icm_state` — Read — https://policylayer.com/tools/dev-avakit-avalanche/icm-state.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

## 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