Maps where given Angular components are imported (modules, specs, templates, styles) so refactors touch every file.
AI agents call build-component-usage-graph to retrieve information from Angular Toolkit MCP 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 an Angular project to identify where components are used. It reads and maps import relationships across files without modifying, executing, or deleting anything. The purpose is to inform refactoring decisions, not perform them. Severity is low as it only reads project structure.
From the tool's definition Maps where given Angular components are imported (modules, specs, templates, styles)
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Maps where given Angular components are imported (modules, specs, templates, styles) so refactors touch every file. It is categorised as a Read tool in the Angular Toolkit MCP MCP Server, which means it retrieves data without modifying state.
Register the Angular Toolkit MCP server in PolicyLayer and add a rule for build-component-usage-graph: 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 Angular Toolkit MCP. Nothing to install.
build-component-usage-graph 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 build-component-usage-graph 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 build-component-usage-graph. 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.
build-component-usage-graph is provided by the Angular Toolkit MCP server (push-based/angular-toolkit-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 →