AI agents call qaradar_should_run to retrieve information from QA Radar without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the server context (QA Radar provides churn, coverage, and test mapping as risk scores) and sibling tools (all appear to be read/query operations), this tool likely determines whether tests should be run for given files — a read/query operation. However, the empty description significantly lowers confidence. The name suggests a decision/query function rather than any write, execute, or destructive action.
From the tool's definition Tool name 'qaradar_should_run' on a server described as providing risk scores for files to test; no description provided.
Attacks that exploit this kind of access
qaradar_should_run. It is categorised as a Read tool in the QA Radar MCP Server, which means it retrieves data without modifying state.
Register the QA Radar MCP server in PolicyLayer and add a rule for qaradar_should_run: 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 QA Radar. Nothing to install.
qaradar_should_run 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 qaradar_should_run 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 qaradar_should_run. 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.
qaradar_should_run is provided by the QA Radar MCP server (qaradar). 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 →