update_run · Testrail MCP: Risk & Policy

WHAT IT DOES

What update_run does on Testrail

AI agents use update_run to create or update resources in Testrail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Testrail environment.

WHY IT NEEDS A POLICY

Why update_run needs a policy

This tool modifies metadata of an existing test run in TestRail (a test management system) in a reversible manner—typical patch/update operations. It does not delete data (which would be Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool name 'update_run' and description 'Patch an existing test run's metadata' indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_run Rate-limited

update_run 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_run": {
      "limits": [
        {
          "counter": "update_run_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, so you can run agents against it safely.

FAQ

Questions about update_run

What does the update_run tool do? +

Patch an existing test run's metadata. Pass only fields you want to change. It is categorised as a Write tool in the Testrail 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_run? +

Register the Testrail MCP server in PolicyLayer and add a rule for update_run: 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. Nothing to install.

What risk level is update_run? +

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

Can I rate-limit update_run? +

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

Set action: deny in the PolicyLayer policy for update_run. 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_run? +

update_run is provided by the Testrail MCP server (sergey-bl/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_run is one line of Testrail'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 →