Get graph information of a module, including importers, imported modules, and compiled result.
AI agents call get-vite-module-info 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 inspects and returns information about module dependencies and compilation metadata in a Vite app. It has no side effects, does not execute code, does not modify files, and does not delete anything. It is purely informational, making it a Read operation with low severity — misuse would only expose internal build structure details without risking data loss or code execution.
From the tool's definition The tool retrieves 'graph information of a module, including importers, imported modules, and compiled result' — these are read operations that query metadata about the build structure without modifying or executing anything.
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 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-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 Vite Plugin. 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 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.