Get the Nuxt configuration, including the ssr, appDir, srcDir, rootDir, alias, runtimeConfig, modules, etc.
AI agents call get-nuxt-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 queries and retrieves Nuxt application configuration metadata without creating, modifying, deleting, or executing anything. It is purely informational for understanding the app structure and settings. The low severity reflects that configuration data alone, without execution capabilities, poses minimal risk even if misused by an agent.
From the tool's definition Tool retrieves configuration data (ssr, appDir, srcDir, rootDir, alias, runtimeConfig, modules, etc.) with no indication of modification or side effects.
Attacks that exploit this kind of access
Get the Nuxt configuration, including the ssr, appDir, srcDir, rootDir, alias, runtimeConfig, modules, etc. 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-nuxt-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-nuxt-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-nuxt-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-nuxt-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-nuxt-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.