AI agents call get_case 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 tool retrieves or queries a test case from TestRail without modifying, deleting, or executing operations. Even without a description, the naming convention strongly indicates a read-only operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name is 'get_case' which indicates a retrieval operation. No description provided, but the naming pattern is consistent with query/fetch operations (contrasted with sibling tools like 'add_case', 'delete_case', 'close_run' which are Write/Destructive).
Documented attack patterns abuse exactly the kind of access get_case 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_case:
{
"version": "1",
"default": "deny",
"tools": {
"get_case": {}
}
}get_case 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_case. 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_case: 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_case 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_case 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_case. 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_case 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.