// SCAN REPORT

Vite Plugin

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 Vite Plugin ↓

TOOL MAP

What Vite Plugin 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 Vite Plugin tools

Write · Medium nuxt-scaffold Scaffolding creates new files in the project directory.

1 of Vite Plugin'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 Vite Plugin

PolicyLayer is an MCP gateway — it sits between your AI agents and Vite Plugin, 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 Vite Plugin — 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 VITE PLUGIN →

Instant setup, no code required.

FULL CATALOGUE

All 7 Vite Plugin 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 Vite Plugin

How do I prevent bulk modifications through Vite Plugin? +

The Vite Plugin 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 Vite Plugin.

How many tools does the Vite Plugin 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 Vite Plugin? +

Register the Vite Plugin 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 Vite Plugin tool call.

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

ENFORCE POLICY ON VITE PLUGIN →

Instant setup, no code required.

7 Vite Plugin tools catalogued and risk-classified — across an index of 43,000+ MCP servers.