vite-build

Runs Vite production build and returns structured output files with sizes.

SERVERDocker SOURCE@paretools/docker

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-docker/vite-build.md

WHAT IT DOES

What vite-build does on Docker

AI agents invoke vite-build to trigger actions in Docker. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why vite-build is rated High

This tool executes an external build process (Vite) whose effects depend on the codebase being built. While not destructive in intent, build processes can consume significant resources, modify the filesystem, and trigger downstream operations. An AI agent with unsupervised access could trigger resource exhaustion or unintended builds.

From the tool's definition Tool name 'vite-build' and description 'Runs Vite production build' indicate execution of a build process with external side effects. The phrase 'returns structured output files' confirms it generates artifacts on the filesystem.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs vite-build safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Docker, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For vite-build, this is the rule to start with:

vite-build Rate-limited

vite-build stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "vite-build": {
      "limits": [
        {
          "counter": "vite-build_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about vite-build

What does the vite-build tool do? +

Runs Vite production build and returns structured output files with sizes. It is categorised as a Execute tool in the Docker MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vite-build? +

Register the Docker MCP server in PolicyLayer and add a rule for vite-build: 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 Docker. Nothing to install.

What risk level is vite-build? +

vite-build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vite-build? +

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

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

vite-build is provided by the Docker MCP server (@paretools/docker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Docker, and thousands of servers like it.

This server

All 202 Docker tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →