arch_generate_report
Genera reporte arquitectonico completo. Parametros: target (directorio, default todo).
This record as markdown: /tools/inggerman-mcps/arch-generate-report.md
What arch_generate_report does on MCP Framework Personal
AI agents invoke arch_generate_report to trigger actions in MCP Framework Personal. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why arch_generate_report is rated High
This tool executes a full architectural analysis across a target directory (defaulting to the entire filesystem), which involves traversing, reading, and processing potentially all files. While it produces a report (read-like), the execution scope is broad and its behavior depends on arguments. The blast radius is high because an AI agent could inadvertently trigger expensive or sensitive directory-wide scans.
From the tool's definition 'Genera reporte arquitectonico completo' (generates complete architectural report) scanning a target directory (default: all)
Attacks that exploit this kind of access
The rule that runs arch_generate_report safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Framework Personal, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For arch_generate_report, this is the rule to start with:
arch_generate_report stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Framework Personal, apply this rule, and every arch_generate_report call is checked against it from then on.
Questions about arch_generate_report
Genera reporte arquitectonico completo. Parametros: target (directorio, default todo). It is categorised as a Execute tool in the MCP Framework Personal MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP Framework Personal MCP server in PolicyLayer and add a rule for arch_generate_report: 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 MCP Framework Personal. Nothing to install.
arch_generate_report is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the arch_generate_report 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_report. 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_report is provided by the MCP Framework Personal MCP server (inggerman/mcps). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Framework Personal, and thousands of servers like it.
Across the catalogue