AI agents call sq_search_hotspots to retrieve information from Sonarcube without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries data about security hotspots from SonarQube. It has no side effects—it does not create, modify, delete, or execute any operations. The action is purely informational, consistent with other sibling tools like sq_get_hotspot, sq_get_issue, and sq_search_issues which are all read operations.
From the tool's definition Tool name 'sq_search_hotspots' and description 'Search security hotspots needing review for a project' indicate querying/retrieving data. The verb 'search' is a read operation that retrieves information about security hotspots without modification.
Attacks that exploit this kind of access
Search security hotspots needing review for a project. It is categorised as a Read tool in the Sonarcube MCP Server, which means it retrieves data without modifying state.
Register the Sonarcube MCP server in PolicyLayer and add a rule for sq_search_hotspots: 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 Sonarcube. Nothing to install.
sq_search_hotspots 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 sq_search_hotspots 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 sq_search_hotspots. 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.
sq_search_hotspots is provided by the Sonarcube MCP server (sonarcube-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 →