update_test_case · TestCollab MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_test_case does on TestCollab MCP Server

AI agents use update_test_case to create or update resources in TestCollab MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TestCollab MCP Server environment.

WHY IT NEEDS A POLICY

Why update_test_case needs a policy

An AI agent can call update_test_case faster than any human can review — one bad instruction and it creates or modifies resources in TestCollab MCP Server by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_test_case Rate-limited

update_test_case 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_test_case": {
      "limits": [
        {
          "counter": "update_test_case_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 TestCollab MCP Server, so you can run agents against it safely.

FAQ

Questions about update_test_case

What does the update_test_case tool do? +

Update an existing test case in TestCollab. Only provided fields will be updated. Tip: Call get_project_context first to resolve suite/tag/custom field names to IDs. Tip: If you need existing steps (e.g., to fill missing expected results), call get_test_case first and then use steps_patch. Required: id (test case ID) Optional fields: - title: New title - suite: Move to different suite - description: New description (HTML) - priority: 0 (Low), 1 (Normal), 2 (High) - steps: Replaces all existing steps - steps_patch: Patch steps by step number (1-based) without replacing all steps - tags: Replaces all existing tags - requirements: Replaces all existing requirements - custom_fields: Update specific custom fields Example: {. It is categorised as a Write tool in the TestCollab 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_test_case? +

Register the TestCollab MCP Server MCP server in PolicyLayer and add a rule for update_test_case: 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 TestCollab MCP Server. Nothing to install.

What risk level is update_test_case? +

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

Can I rate-limit update_test_case? +

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

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

update_test_case is provided by the TestCollab MCP Server MCP server (tcsoftinc/testcollab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.