Get read-only SonarQube quality gate status for a project.
AI agents call get_quality_gate_status 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 quality gate status information from SonarQube without modifying any data. Quality gate status is a read-only query of project quality metrics. There are no side effects, no code execution, no data modification, and no destructive operations. This is a straightforward data retrieval operation with minimal risk.
From the tool's definition Tool description explicitly states 'Get read-only SonarQube quality gate status for a project' and the server is described as 'Read-only MCP server that exposes SonarQube Web API tools for issue retrieval'.
Attacks that exploit this kind of access
Get read-only SonarQube quality gate status for a project. 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_quality_gate_status: 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_quality_gate_status 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_gate_status 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_gate_status. 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_gate_status 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 →