get_component_tree
Build a component render tree starting from a given .vue file. Use to visualize parent-child component hierarchy. Read-only. Returns JSON: { root, children: [{ component, props, slots, depth }], totalComponents }.
This record as markdown: /tools/nikolai-vysotskyi-trace-mcp/get-component-tree.md
What get_component_tree does on Trace
AI agents call get_component_tree to retrieve information from Trace without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_component_tree is rated Low
This tool queries source code structure to generate a dependency/hierarchy visualization. It performs no writes, no destructive operations, no code execution, and no external side effects. The 'Build' verb here means 'construct a view of' existing data, not 'create' new artifacts.
From the tool's definition Tool description explicitly states 'Read-only' and 'Build a component render tree' / 'visualize parent-child component hierarchy' / 'Returns JSON' — purely retrieves and displays structural information about Vue component relationships without modifying code…
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs get_component_tree safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Trace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_component_tree, this is the rule to start with:
get_component_tree is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Trace, apply this rule, and every get_component_tree call is checked against it from then on.
Questions about get_component_tree
Build a component render tree starting from a given .vue file. Use to visualize parent-child component hierarchy. Read-only. Returns JSON: { root, children: [{ component, props, slots, depth }], totalComponents }. It is categorised as a Read tool in the Trace MCP Server, which means it retrieves data without modifying state.
Register the Trace MCP server in PolicyLayer and add a rule for get_component_tree: 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 Trace. Nothing to install.
get_component_tree 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 get_component_tree 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 get_component_tree. 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.
get_component_tree is provided by the Trace MCP server (nikolai-vysotskyi/trace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Trace, and thousands of servers like it.
This server
Across the catalogue