Get graph information of a module, including importers, imported modules, and compiled result.
AI agents call get-vite-module-info 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 retrieves and displays dependency graph information and compilation metadata about Vite modules. It performs no writes, deletions, code execution, or financial operations—purely informational queries on the development build system. No side effects beyond providing introspection data.
From the tool's definition Tool name 'get-vite-module-info' and description 'Get graph information of a module' indicate retrieval only.
Attacks that exploit this kind of access
Get graph information of a module, including importers, imported modules, and compiled result. 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-module-info: 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-module-info 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-module-info 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-module-info. 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-module-info 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 →