// SCAN REPORT

Nuxt Mcp Dev

7 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 26 Jun 2026

1 can modify or destroy data

6 read-only

7 tools total

Community server · catalogue entry verified 26/06/2026

How to control Nuxt Mcp Dev ↓

TOOL MAP

What Nuxt Mcp Dev exposes to your agents

Read (6) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Nuxt Mcp Dev tools

Write · Medium nuxt-scaffold This tool creates new files (components, pages, layouts, middleware) in the project.

1 of Nuxt Mcp Dev's 7 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Nuxt Mcp Dev

PolicyLayer is an MCP gateway — it sits between your AI agents and Nuxt Mcp Dev, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "nuxt-scaffold": {
    "limits": [
      {
        "counter": "nuxt-scaffold_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get-nuxt-config": {
    "limits": [
      {
        "counter": "get-nuxt-config_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Nuxt Mcp Dev — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON NUXT MCP DEV →

Instant setup, no code required.

FULL CATALOGUE

All 7 Nuxt Mcp Dev tools

WRITE 1 tools

Write nuxt-scaffold Scaffold a new component/page/layout/middleware etc. in the current Nuxt project.

READ 6 tools

Read get-nuxt-config Get the Nuxt configuration, including the ssr, appDir, srcDir, rootDir, alias, runtimeConfig, modules, etc. Read get-vite-config Get the Vite config digest, including the root, resolve, plugins, and environment names. Read get-vite-module-info Get graph information of a module, including importers, imported modules, and compiled result. Read list-nuxt-auto-imports-items List auto-imports items, when importing new functions to the code, check available items from this tool. Read list-nuxt-components List registered components in the Nuxt app. When adding importing new components, check available components f Read list-nuxt-pages List registered pages and their metadata in the Nuxt app.

FAQ

Questions about Nuxt Mcp Dev

How do I prevent bulk modifications through Nuxt Mcp Dev? +

The Nuxt Mcp Dev server has 1 write tools including nuxt-scaffold. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Nuxt Mcp Dev.

How many tools does the Nuxt Mcp Dev MCP server expose? +

7 tools across 1 categories: Read. 6 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Nuxt Mcp Dev? +

Register the Nuxt Mcp Dev MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Nuxt Mcp Dev tool call.

Deterministic rules across all 7 Nuxt Mcp Dev tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NUXT MCP DEV →

Instant setup, no code required.

7 Nuxt Mcp Dev tools catalogued and risk-classified — across an index of 43,000+ MCP servers.