Search read-only SonarQube issues through /api/issues/search.
AI agents call search_sonar_issues 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 and queries SonarQube issue data with no side effects, no data modification capability, and no external execution or financial impact. It fits the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The read-only constraint and search-only functionality make this low severity.
From the tool's definition Tool description explicitly states 'Search read-only SonarQube issues through /api/issues/search.' The 'read-only' qualifier and 'search' verb both confirm retrieval without modification. Server description confirms the entire server is 'read-only MCP server.'
Attacks that exploit this kind of access
Search read-only SonarQube issues through /api/issues/search. 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 search_sonar_issues: 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.
search_sonar_issues 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 search_sonar_issues 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 search_sonar_issues. 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.
search_sonar_issues 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 →