AI agents use add_case to create or update resources in TestRail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TestRail MCP Server environment.
The 'add_' prefix and sibling context strongly indicate this creates new data (test cases) in TestRail. Creation of test case data is reversible (can be deleted via the 'delete_case' sibling tool), making it Write rather than Destructive. Confidence is lowered to 0.85 due to empty description—if the tool's actual implementation differs substantially from its name, the classification could shift.
From the tool's definition Tool named 'add_case' with no description. Sibling tools include 'add_project', 'add_run', 'add_result', and 'add_dataset', which are clearly Write operations. The 'add_' prefix indicates data creation.
Documented attack patterns abuse exactly the kind of access add_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 add_case:
{
"version": "1",
"default": "deny",
"tools": {
"add_case": {
"limits": [
{
"counter": "add_case_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_case stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
add_case. It is categorised as a Write tool in the TestRail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for add_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.
add_case is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_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.