add_attachment_to_plan_entry · TestRail MCP Server MCP

WHAT IT DOES

What add_attachment_to_plan_entry does on TestRail MCP Server

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

This tool creates new data (an attachment relationship) within TestRail, modifying the state of a plan entry. It is a Write operation because it adds/modifies content reversibly.

From the tool's definition Tool name contains 'add_attachment' and description states 'Add an attachment to a test plan entry' — this creates/modifies data by attaching a file to an existing plan entry, which is reversible (attachment can be removed).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_attachment_to_plan_entry Rate-limited

add_attachment_to_plan_entry 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_entry": {
      "limits": [
        {
          "counter": "add_attachment_to_plan_entry_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_entry

What does the add_attachment_to_plan_entry tool do? +

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

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

add_attachment_to_plan_entry 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_entry? +

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

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

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