list_issue_authors
AI agents call list_issue_authors 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 metadata (authors) from SonarCloud issues without modifying state. The empty description lowers confidence slightly, but the naming convention and sibling context strongly indicate it is a Read operation with no side effects.
From the tool's definition Tool name 'list_issue_authors' indicates retrieval/enumeration of author data from SonarCloud issues. No description provided, but the 'list_' prefix and context among sibling Read tools (search_hotspots, search_my_sonarqube_projects, list_quality_gates)…
Attacks that exploit this kind of access
list_issue_authors. 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 list_issue_authors: 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.
list_issue_authors 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 list_issue_authors 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 list_issue_authors. 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.
list_issue_authors 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 →