run_testrail_command · TestRail MCP Server MCP

WHAT IT DOES

What run_testrail_command does on TestRail MCP Server

AI agents invoke run_testrail_command to trigger actions in TestRail MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_testrail_command needs a policy

This tool runs commands against TestRail, which could modify test cases, runs, and results depending on what commands an AI agent constructs. While it may not directly delete data (which would be Destructive), the ability to execute arbitrary API commands without specification creates high blast radius if the agent calls methods that alter test infrastructure or results.

From the tool's definition Tool name 'run_testrail_command' indicates execution of arbitrary TestRail API commands. Description is empty, but context shows this server manages test cases, runs, and results.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_testrail_command Rate-limited

run_testrail_command stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_testrail_command": {
      "limits": [
        {
          "counter": "run_testrail_command_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_testrail_command

What does the run_testrail_command tool do? +

run_testrail_command. It is categorised as a Execute tool in the TestRail MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_testrail_command? +

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

run_testrail_command is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_testrail_command? +

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

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

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