search_my_sonarqube_projects
AI agents call search_my_sonarqube_projects to retrieve information from Mcp Sonarcloud without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or lists projects from SonarCloud—a read-only query operation with no side effects. The naming convention ('search') and context of peer tools (all retrieval-focused) confirm it retrieves data without modification, deletion, or execution. Low severity due to limited blast radius of querying project metadata.
From the tool's definition Tool name 'search_my_sonarqube_projects' indicates a search/query operation. Server description mentions 'interaction with SonarCloud projects' and sibling tools include 'search_hotspots', 'search_quality_gates', and list operations, all of which are Read…
Attacks that exploit this kind of access
search_my_sonarqube_projects. It is categorised as a Read tool in the Mcp Sonarcloud MCP Server, which means it retrieves data without modifying state.
Register the Mcp Sonarcloud MCP server in PolicyLayer and add a rule for search_my_sonarqube_projects: 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 Mcp Sonarcloud. Nothing to install.
search_my_sonarqube_projects 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_my_sonarqube_projects 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_my_sonarqube_projects. 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_my_sonarqube_projects is provided by the Mcp Sonarcloud MCP server (lukleh/mcp-sonarcloud). 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 →