Get read-only SonarQube source lines for a component.
AI agents call get_sonar_sources to retrieve information from Sonarqube Api without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves source code lines from SonarQube without modifying, deleting, or executing anything. The 'read-only' qualifier in the description and the passive 'get' verb confirm it performs a simple data query operation. Severity is low because exposure of source code is a minimal security risk in the context of an MCP server used for code analysis and fixing.
From the tool's definition Tool name 'get_sonar_sources' and description 'Get read-only SonarQube source lines for a component' explicitly indicate read-only data retrieval with no side effects.
Attacks that exploit this kind of access
Get read-only SonarQube source lines for a component. It is categorised as a Read tool in the Sonarqube Api MCP Server, which means it retrieves data without modifying state.
Register the Sonarqube Api MCP server in PolicyLayer and add a rule for get_sonar_sources: 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 Sonarqube Api. Nothing to install.
get_sonar_sources 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_sonar_sources 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_sonar_sources. 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_sonar_sources is provided by the Sonarqube Api MCP server (yozzone/sonarqube-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 →