Get the Vite config digest, including the root, resolve, plugins, and environment names.
AI agents call get-vite-config to retrieve information from Nuxt Mcp Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and returns Vite configuration metadata. It queries application settings without side effects, matching the Read category pattern (get, fetch, retrieve). The scope is limited to build configuration inspection, posing minimal security risk even if exposed to an AI agent.
From the tool's definition Tool retrieves configuration information: 'Get the Vite config digest, including the root, resolve, plugins, and environment names.' No data modification, deletion, or code execution is described.
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 Nuxt Mcp Dev MCP Server, which means it retrieves data without modifying state.
Register the Nuxt Mcp Dev 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 Nuxt Mcp Dev. 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 Nuxt Mcp Dev MCP server (nuxt-mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →