Analyze code and return detailed findings about legacy imports, components, props, hooks and Tailwind patterns.
AI agents call analyze_file to retrieve information from HeroUI Migration MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static code analysis—scanning and examining code to identify legacy patterns, components, props, hooks, and Tailwind usage. It has no side effects; it does not modify files, execute code, delete data, or trigger external operations. It is a pure information-retrieval tool used to support migration planning.
From the tool's definition Tool description states it 'Analyze[s] code and return[s] detailed findings' without any modification, deletion, or execution capability. The verb 'analyze' and 'return' indicate read-only operations that retrieve information about code patterns.
Documented attack patterns abuse exactly the kind of access analyze_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and HeroUI Migration MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for analyze_file:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_file": {}
}
}analyze_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Analyze code and return detailed findings about legacy imports, components, props, hooks and Tailwind patterns. It is categorised as a Read tool in the HeroUI Migration MCP MCP Server, which means it retrieves data without modifying state.
Register the HeroUI Migration MCP server in PolicyLayer and add a rule for analyze_file: 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 HeroUI Migration MCP. Nothing to install.
analyze_file 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 analyze_file 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 analyze_file. 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.
analyze_file is provided by the HeroUI Migration MCP server (sctg-development/heroui-migration-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from HeroUI Migration MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 HeroUI Migration MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.