update_plan · TestRail MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_plan does on TestRail MCP Server

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

This tool modifies existing test plan data reversibly. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), or move money (would be Financial). Within a test management context, updating plans affects test tracking and reporting but is a standard administrative modification.

From the tool's definition Tool name 'update_plan' and description 'Update an existing test plan' indicate modification of existing data in TestRail.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_plan Rate-limited

update_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": {
    "update_plan": {
      "limits": [
        {
          "counter": "update_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 update_plan

What does the update_plan tool do? +

Update an existing 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 update_plan? +

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

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

Can I rate-limit update_plan? +

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

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

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