add_attachment_to_plan · TestRail MCP Server MCP

WHAT IT DOES

What add_attachment_to_plan does on TestRail MCP Server

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

This tool creates new data (file attachment) associated with an existing test plan, which is a write operation. It modifies the plan's state by adding content to it. Severity is medium because attachment additions are reversible (attachments can be deleted) and the blast radius is limited to test plan documentation/artifacts rather than test execution or deletion of core data.

From the tool's definition Tool name 'add_attachment_to_plan' and description 'Add an attachment to a test plan' indicate creation/modification of test plan data by attaching files.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_attachment_to_plan Rate-limited

add_attachment_to_plan 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_attachment_to_plan": {
      "limits": [
        {
          "counter": "add_attachment_to_plan_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_attachment_to_plan

What does the add_attachment_to_plan tool do? +

Add an attachment to a test plan. 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_attachment_to_plan? +

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

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

Can I rate-limit add_attachment_to_plan? +

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

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

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