(legacy) Returns detailed migration guidance for a component by comparing v2 and v3 docs.
AI agents call get_migration_guide 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 documentation retrieval and comparison to provide guidance to developers. It does not execute scripts, modify user code, delete data, or trigger external operations. While it assists with migration tasks, the actual execution of migrations remains the developer's responsibility.
From the tool's definition Tool returns migration guidance by comparing documentation; uses verbs 'Returns' and 'comparing' indicating data retrieval with no modification or execution of code against user systems.
Documented attack patterns abuse exactly the kind of access get_migration_guide 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 get_migration_guide:
{
"version": "1",
"default": "deny",
"tools": {
"get_migration_guide": {}
}
} get_migration_guide 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.
(legacy) Returns detailed migration guidance for a component by comparing v2 and v3 docs. 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 get_migration_guide: 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.
get_migration_guide 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_migration_guide 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_migration_guide. 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_migration_guide 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.