copy_cases_to_section · TestRail MCP Server MCP

WHAT IT DOES

What copy_cases_to_section does on TestRail MCP Server

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

This tool creates new test case records in a destination section by copying existing cases. It is reversible (the copied cases can be deleted), so it falls under Write rather than Destructive. The blast radius is medium because incorrect copying could create unwanted test case duplicates requiring cleanup, but the impact is limited to test data and does not affect production systems or financial transactions.

From the tool's definition Tool name is 'copy_cases_to_section' and description states 'Copy test cases to another section'. The verb 'copy' indicates creation of new data (duplicated test cases in a target section).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_cases_to_section Rate-limited

copy_cases_to_section 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": {
    "copy_cases_to_section": {
      "limits": [
        {
          "counter": "copy_cases_to_section_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 copy_cases_to_section

What does the copy_cases_to_section tool do? +

Copy test cases to another section. 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 copy_cases_to_section? +

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

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

Can I rate-limit copy_cases_to_section? +

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

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

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