AI agents call get_cases 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.
The 'get' prefix strongly indicates this tool retrieves test case data without modification. Even without a description, 'get' is unambiguous in software conventions. No side effects, destructive actions, code execution, or financial implications are implied. Severity is low because retrieving test case metadata poses minimal risk—it may expose test design information but does not modify state or commit actions.
From the tool's definition Tool name 'get_cases' indicates a retrieval operation consistent with standard CRUD naming conventions (get = read). No description provided, but the verb 'get' universally denotes read-only data retrieval.
Documented attack patterns abuse exactly the kind of access get_cases gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TestRail MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_cases:
{
"version": "1",
"default": "deny",
"tools": {
"get_cases": {}
}
}get_cases is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_cases. 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 get_cases: 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.
get_cases 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_cases 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_cases. 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_cases is provided by the TestRail MCP Server MCP server (sker65/testrail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TestRail MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
29 TestRail MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.