Get read-only SonarQube rule details.
AI agents call get_rule_details 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 static rule metadata from SonarQube (e.g., rule definitions, descriptions, severity levels) with no side effects. It is purely informational and supports code analysis without modifying any state. Classification as Read is appropriate with low severity due to the absence of any dangerous blast radius if misused by an AI agent.
From the tool's definition Tool name 'get_rule_details' and description explicitly states 'read-only' SonarQube rule details retrieval.
Attacks that exploit this kind of access
Get read-only SonarQube rule details. 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_rule_details: 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_rule_details 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_rule_details 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_rule_details. 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_rule_details 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 →