get_issue_changelog
AI agents call get_issue_changelog 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.
The tool retrieves changelog data for an issue, which is a read-only query operation with no side effects or data modification. While the description is empty, the naming pattern and context within the SonarCloud analysis server (which appears to be primarily for querying code quality and security data) indicate this is an informational retrieval tool.
From the tool's definition Tool name 'get_issue_changelog' indicates retrieval of historical data about issues. The sibling tools on this server (search_hotspots, get_project_quality_gate_status, list_issue_authors, etc.) are all Read operations that query SonarCloud data without…
Attacks that exploit this kind of access
get_issue_changelog. 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 get_issue_changelog: 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.
get_issue_changelog 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_issue_changelog 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_issue_changelog. 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_issue_changelog 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 →