This record as markdown: /tools/io-github-dave-london-git/vite-build.md
What vite-build does on Git
AI agents invoke vite-build to trigger actions in Git. 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.
Why vite-build is rated High
This tool triggers external operations (Vite build system) whose effects cannot be predetermined and depend on the provided arguments and project state. While it produces outputs rather than modifying persistent data structures, it runs code execution on the system.
From the tool's definition Tool "Runs Vite production build" - executes a build process with side effects that depend on the codebase and configuration arguments
Attacks that exploit this kind of access
The rule that runs vite-build safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Git, 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 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every vite-build call is checked against it from then on.
Questions about vite-build
Runs Vite production build and returns structured output files with sizes. It is categorised as a Execute tool in the Git MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Git 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 Git. Nothing to install.
vite-build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
vite-build is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Git, and thousands of servers like it.
This server
Across the catalogue