update_case · TestRail MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_case does on TestRail MCP Server

AI agents use update_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 update_case needs a policy

The tool creates or modifies data (test case) in a reversible manner without deleting or destroying information. While it could impact test case definitions used across projects, updates to test metadata are generally reversible through subsequent edits.

From the tool's definition Tool name is 'update_case' and description states 'Update an existing test case' - this modifies existing data in TestRail reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_case Rate-limited

update_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": {
    "update_case": {
      "limits": [
        {
          "counter": "update_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 update_case

What does the update_case tool do? +

Update an existing test 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.

How do I enforce a policy on update_case? +

Register the TestRail MCP Server MCP server in PolicyLayer and add a rule for update_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 update_case? +

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

Can I rate-limit update_case? +

Yes. Add a rate_limit block to the update_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 update_case completely? +

Set action: deny in the PolicyLayer policy for update_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 update_case? +

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

// THE FULL RECORD

update_case is one line of TestRail MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →