AI agents call get_quality_profile to retrieve information from Sonarqube without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns configuration data (a quality profile) for a SonarQube project. It has no capability to modify, delete, or execute operations—it is purely informational. The low severity reflects minimal blast radius: worst case, an agent learns about code quality standards, which poses no security or operational risk. Confidence is high because the description is explicit and unambiguous.
From the tool's definition Tool name 'get_quality_profile' and description 'Get quality profile for a project' indicate a retrieval operation with no mutation or side effects. The verb 'Get' is explicitly used, matching the Read category pattern of 'get, fetch, retrieve'.
Attacks that exploit this kind of access
Get quality profile for a project. It is categorised as a Read tool in the Sonarqube MCP Server, which means it retrieves data without modifying state.
Register the Sonarqube MCP server in PolicyLayer and add a rule for get_quality_profile: 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. Nothing to install.
get_quality_profile 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_quality_profile 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_quality_profile. 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_quality_profile is provided by the Sonarqube MCP server (@miocid152/sonarqube-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 →