Generate a visual HTML architecture dashboard — layers, dependency graph, tech stack, and class overview. Opens in any browser.
AI agents call generate_dashboard to retrieve information from Spring Api Intel without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs static analysis of the codebase and generates an HTML report for visualization. It reads and analyzes existing code structure without modifying, deleting, or executing anything. The output is a read-only HTML dashboard. Severity is low because misuse would at most expose architectural details of the codebase.
From the tool's definition Generate a visual HTML architecture dashboard — layers, dependency graph, tech stack, and class overview. Opens in any browser.
Attacks that exploit this kind of access
Generate a visual HTML architecture dashboard — layers, dependency graph, tech stack, and class overview. Opens in any browser. It is categorised as a Read tool in the Spring Api Intel MCP Server, which means it retrieves data without modifying state.
Register the Spring Api Intel MCP server in PolicyLayer and add a rule for generate_dashboard: 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 Spring Api Intel. Nothing to install.
generate_dashboard 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 generate_dashboard 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 generate_dashboard. 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.
generate_dashboard is provided by the Spring Api Intel MCP server (mparth14/spring-api-intel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →