Get the Vite config digest, including the root, resolve, plugins, and environment names.
AI agents call get-vite-config to retrieve information from Vite Plugin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and queries existing Vite configuration metadata. It has no side effects, does not execute code, does not modify data, and does not trigger external operations. The blast radius of misuse is minimal — an AI could only learn about the app's build configuration, not alter it or cause damage.
From the tool's definition Tool name is 'get-vite-config' and description states it 'Get[s] the Vite config digest' — a retrieval operation with no modification or execution. Returns static configuration information (root, resolve, plugins, environment names).
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Get the Vite config digest, including the root, resolve, plugins, and environment names. It is categorised as a Read tool in the Vite Plugin MCP Server, which means it retrieves data without modifying state.
Register the Vite Plugin MCP server in PolicyLayer and add a rule for get-vite-config: 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 Vite Plugin. Nothing to install.
get-vite-config is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get-vite-config 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 get-vite-config. 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.
get-vite-config is provided by the Vite Plugin MCP server (vite-plugin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.