add_section · TestRail MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_section does on TestRail MCP Server

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

The tool creates new test organization data (sections) within TestRail. This is a reversible Write operation—sections can be modified, moved, or deleted afterward. It has a moderate blast radius (an AI agent creating excessive or malformed sections could clutter the test organization), but no permanent data loss or external effects. It does not execute code, delete data irreversibly, or move money.

From the tool's definition Tool name 'add_section' with description 'Create a new section' indicates data creation. The TestRail context shows this creates a test section within projects, which is a reversible operation (sections can be deleted or modified later).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_section Rate-limited

add_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": {
    "add_section": {
      "limits": [
        {
          "counter": "add_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 add_section

What does the add_section tool do? +

Create a new 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 add_section? +

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

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

Can I rate-limit add_section? +

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

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

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