AI agents call get_sonar_rules 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.
The tool retrieves and queries SonarQube rules data without creating, modifying, deleting, or executing any operations. It is a simple read operation with pagination support. Severity is low because misuse would only result in unauthorized information disclosure of rule definitions, with no side effects on systems or data integrity.
From the tool's definition Tool description states 'Get SonarQube rules with pagination' and 'Returns page info to guide next calls' — this is a retrieval operation with no modification of data.
Attacks that exploit this kind of access
Get SonarQube rules with pagination. Use multiple calls with different page numbers to get all rules and avoid character limits. Returns page info to guide next calls. 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_sonar_rules: 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_sonar_rules 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_rules 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_rules. 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_rules 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 →