add_results_for_cases · TestRail MCP Server MCP

WHAT IT DOES

What add_results_for_cases does on TestRail MCP Server

AI agents use add_results_for_cases 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.

WHY IT NEEDS A POLICY

Why add_results_for_cases needs a policy

This tool creates or modifies test result records within TestRail, which is a reversible data operation. While test results are important metadata in a testing workflow, adding/updating results does not delete data, execute arbitrary code, move money, or trigger irreversible system changes.

From the tool's definition Tool name 'add_results_for_cases' and description 'Add multiple test results for cases in a run' indicate creation/modification of test result data. The 'add' verb and action of recording test results are reversible operations typical of Write category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_results_for_cases Rate-limited

add_results_for_cases 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_results_for_cases": {
      "limits": [
        {
          "counter": "add_results_for_cases_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TestRail MCP Server, so you can run agents against it safely.

FAQ

Questions about add_results_for_cases

What does the add_results_for_cases tool do? +

Add multiple test results for cases in a run. 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.

How do I enforce a policy on add_results_for_cases? +

Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for add_results_for_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.

What risk level is add_results_for_cases? +

add_results_for_cases is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_results_for_cases? +

Yes. Add a rate_limit block to the add_results_for_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.

How do I block add_results_for_cases completely? +

Set action: deny in the PolicyLayer policy for add_results_for_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.

What MCP server provides add_results_for_cases? +

add_results_for_cases is provided by the TestRail MCP Server MCP server (tenbarrel6/testrail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.