close_run · TestRail MCP Server MCP: Risk & Policy

WHAT IT DOES

What close_run does on TestRail MCP Server

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

Closing a test run modifies its status/state but does not irreversibly delete data or prevent undo (the run can typically be reopened). This is a reversible write operation that changes test run metadata rather than executing arbitrary code or deleting data. Severity is medium because closing a run could impact team workflows and test result tracking, but the blast radius is contained to a single run's state.

From the tool's definition Tool name 'close_run' with description 'Close a test run' indicates a state modification operation on an existing test run resource in TestRail.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

close_run Rate-limited

close_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": {
    "close_run": {
      "limits": [
        {
          "counter": "close_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about close_run

What does the close_run tool do? +

Close a test 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 close_run? +

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

What risk level is close_run? +

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

Can I rate-limit close_run? +

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

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

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