add_plan_entry · TestRail MCP Server MCP: Risk & Policy

WHAT IT DOES

What add_plan_entry does on TestRail MCP Server

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

This tool creates new test plan entries by adding test runs to plans, which is a reversible write operation. It modifies existing test plan structures but does not execute tests, delete data, or move resources. The blast radius is medium because incorrect additions could corrupt test planning workflows and require manual remediation, but changes are reversible through removal or modification.

From the tool's definition Tool name 'add_plan_entry' and description 'Add test runs to a test plan' indicate creation/modification of test plan data through the TestRail API.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_plan_entry Rate-limited

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

What does the add_plan_entry tool do? +

Add test runs 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_plan_entry? +

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

add_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_plan_entry? +

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

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

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