AI agents call sq_get_measures_history 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 metrics and historical data from SonarQube for analysis purposes. It has no side effects—it does not execute code, modify data, delete records, or trigger external operations. The data returned is read-only telemetry about code quality over time.
From the tool's definition Tool name 'sq_get_measures_history' and description 'Get metrics history over time to track trends and regressions' indicate retrieval of historical data without modification.
Attacks that exploit this kind of access
Get metrics history over time to track trends and regressions. 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_get_measures_history: 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_get_measures_history 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_get_measures_history 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_get_measures_history. 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_get_measures_history 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 →