Extract code coverage data from the most recent test run. Shows covered/uncovered lines per class.
AI agents call get_coverage to retrieve information from Squirex Dev without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves pre-computed code coverage metrics from a completed test run. It performs no modifications, deletions, code execution, or financial operations. The action is purely informational—reading test coverage statistics. The low severity reflects minimal risk even if misused by an agent, as accessing coverage data presents no destructive or operational hazards.
From the tool's definition Tool name 'get_coverage' and description 'Extract code coverage data from the most recent test run' indicate retrieval of existing metrics without modification or execution of code.
Attacks that exploit this kind of access
Extract code coverage data from the most recent test run. Shows covered/uncovered lines per class. It is categorised as a Read tool in the Squirex Dev MCP Server, which means it retrieves data without modifying state.
Register the Squirex Dev MCP server in PolicyLayer and add a rule for get_coverage: 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 Squirex Dev. Nothing to install.
get_coverage 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_coverage 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_coverage. 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_coverage is provided by the Squirex Dev MCP server (squirex-dev/squirex-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 →