update_milestone · TestRail MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_milestone does on TestRail MCP Server

AI agents use update_milestone 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_milestone needs a policy

This tool modifies test management metadata (milestones) in a test management system. Updates are non-destructive and reversible, placing it in the Write category. Severity is medium because incorrect milestone updates could affect project timelines and test tracking, but the impact is limited to planning metadata rather than test results or financial systems.

From the tool's definition Tool name 'update_milestone' and description 'Update milestone (enhanced)' indicate modification of existing milestone data within TestRail. The action is reversible—milestones can be updated again or reverted. No deletion or destruction occurs.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_milestone Rate-limited

update_milestone 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_milestone": {
      "limits": [
        {
          "counter": "update_milestone_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_milestone

What does the update_milestone tool do? +

Update milestone (enhanced). 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_milestone? +

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

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

Can I rate-limit update_milestone? +

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

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

update_milestone is provided by the TestRail MCP Server MCP server (samuelvinay91/testrail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.