AI agents call sq_get_component_tree to retrieve information from Sonarcube without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays project structure and quality metrics. It performs a read-only operation on SonarQube data without side effects. No data is modified, deleted, executed, or any financial action is taken. The verb 'Get' and action of querying metrics confirm this is a Read category tool with low severity risk.
From the tool's definition Tool name 'sq_get_component_tree' and description 'Get project file tree with metrics — find files with worst coverage or most issues' indicate retrieval and querying of existing data (file tree structure and metrics) with no modification, creation, deletion,…
Attacks that exploit this kind of access
Get project file tree with metrics — find files with worst coverage or most issues. It is categorised as a Read tool in the Sonarcube MCP Server, which means it retrieves data without modifying state.
Register the Sonarcube MCP server in PolicyLayer and add a rule for sq_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 Sonarcube. Nothing to install.
sq_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 sq_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 sq_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.
sq_get_component_tree is provided by the Sonarcube MCP server (sonarcube-mcp-server). 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 →