add_result_for_case · TestRail MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_result_for_case does on TestRail MCP Server

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

WHY IT NEEDS A POLICY

Why add_result_for_case needs a policy

The tool creates or modifies test result records in TestRail, which is a write operation. While it adds data to a test management system, the operation is reversible (results can be updated or removed). It does not execute arbitrary code, delete data irreversibly, move money, or trigger external systems—it simply records test outcomes within the TestRail database.

From the tool's definition Tool name 'add_result_for_case' and description 'Add a test result for a specific case in a run' indicate creation of test result data within TestRail. This is a reversible write operation that adds new records to the test management system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_result_for_case Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_result_for_case": {
      "limits": [
        {
          "counter": "add_result_for_case_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_result_for_case

What does the add_result_for_case tool do? +

Add a test result for a specific case 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_result_for_case? +

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

What risk level is add_result_for_case? +

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

Can I rate-limit add_result_for_case? +

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

How do I block add_result_for_case completely? +

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

What MCP server provides add_result_for_case? +

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