Analyze test case metrics and health
AI agents call analyze_case_metrics to retrieve information from TestRail MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and evaluates existing test case metrics and health data without creating, modifying, deleting, or executing any external operations. It is purely analytical and informational in nature, making it a Read category risk with low severity.
From the tool's definition Tool name 'analyze_case_metrics' and description 'Analyze test case metrics and health' indicates data retrieval and analysis with no modification or side effects. The verb 'analyze' combined with 'metrics' and 'health' describes a read-only query operation.
Attacks that exploit this kind of access
Analyze test case metrics and health. It is categorised as a Read tool in the TestRail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for analyze_case_metrics: 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 TestRail MCP Server. Nothing to install.
analyze_case_metrics 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 analyze_case_metrics 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 analyze_case_metrics. 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.
analyze_case_metrics is provided by the TestRail MCP Server MCP server (samuelvinay91/testrail-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 →