List auto-imports items, when importing new functions to the code, check available items from this tool.
AI agents call list-nuxt-auto-imports-items 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 information about available auto-imports in a Nuxt application. It performs a read-only operation with no side effects, data modification, code execution, or destructive actions. The blast radius of misuse is minimal since it only exposes metadata about available imports.
From the tool's definition 'List auto-imports items' – retrieves and queries available auto-import functions without modifying any data or triggering external operations.
Attacks that exploit this kind of access
List auto-imports items, when importing new functions to the code, check available items from this tool. 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 list-nuxt-auto-imports-items: 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.
list-nuxt-auto-imports-items 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 list-nuxt-auto-imports-items 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 list-nuxt-auto-imports-items. 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.
list-nuxt-auto-imports-items 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.