arch_generate_docs
Generate comprehensive architecture documentation from project analysis (Pro)
This record as markdown: /tools/barnburner121-plugin-hub-mcp/arch-generate-docs.md
What arch_generate_docs does on Plugin Hub
AI agents use arch_generate_docs to create or update resources in Plugin Hub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Plugin Hub environment.
Why arch_generate_docs is rated Medium
An AI agent can call arch_generate_docs faster than any human can review: one bad instruction and it creates or modifies resources in Plugin Hub by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs arch_generate_docs safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Plugin Hub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For arch_generate_docs, this is the rule to start with:
arch_generate_docs stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Plugin Hub, apply this rule, and every arch_generate_docs call is checked against it from then on.
Questions about arch_generate_docs
Generate comprehensive architecture documentation from project analysis (Pro). It is categorised as a Write tool in the Plugin Hub MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Plugin Hub MCP server in PolicyLayer and add a rule for arch_generate_docs: 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 Plugin Hub. Nothing to install.
arch_generate_docs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the arch_generate_docs 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 arch_generate_docs. 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.
arch_generate_docs is provided by the Plugin Hub MCP server (@barnburner121/plugin-hub-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Plugin Hub, and thousands of servers like it.
This server
Across the catalogue