Lists files present in data/generated after running the HeroUI v3 generator.
AI agents call list_generated_v3_outputs 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 is a pure read operation. It queries the file system to enumerate outputs from a prior generation step but produces no side effects. It does not execute code, modify files, delete data, or trigger external operations. Blast radius if misused is minimal (information disclosure only).
From the tool's definition The tool description states it 'Lists files present in data/generated' — a query operation that retrieves or enumerates data without modifying, creating, or deleting anything.
Documented attack patterns abuse exactly the kind of access list_generated_v3_outputs 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 list_generated_v3_outputs:
{
"version": "1",
"default": "deny",
"tools": {
"list_generated_v3_outputs": {}
}
} list_generated_v3_outputs 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.
Lists files present in data/generated after running the HeroUI v3 generator. 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 list_generated_v3_outputs: 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.
list_generated_v3_outputs 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_generated_v3_outputs 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_generated_v3_outputs. 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_generated_v3_outputs 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.