Reads one generated HeroUI v3 LLM output file.
AI agents call read_generated_v3_doc 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 retrieves or queries existing generated documentation files without modifying, deleting, or executing operations. It fits the Read category: retrieves data with no side effects. The blast radius is minimal as it only accesses generated documentation relevant to the migration process. Severity is low because reading documentation cannot cause harm to the project or infrastructure.
From the tool's definition Tool name contains 'read' and description states 'Reads one generated HeroUI v3 LLM output file' — explicitly a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access read_generated_v3_doc 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 read_generated_v3_doc:
{
"version": "1",
"default": "deny",
"tools": {
"read_generated_v3_doc": {}
}
}read_generated_v3_doc 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.
Reads one generated HeroUI v3 LLM output file. 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 read_generated_v3_doc: 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.
read_generated_v3_doc 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 read_generated_v3_doc 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 read_generated_v3_doc. 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.
read_generated_v3_doc 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.