testcase_update · Testops MCP: Risk & Policy

WHAT IT DOES

What testcase_update does on Testops

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

WHY IT NEEDS A POLICY

Why testcase_update needs a policy

The tool creates or modifies test case data reversibly (update operation). While it changes test case properties, these changes are not destructive (can be reverted) and do not execute code or move money. This fits the Write category. Severity is medium because corrupting test case metadata could impact test reporting and CI/CD workflows, but effects are contained and reversible.

From the tool's definition Tool description explicitly states 'Update test case metadata (name, description, status, tags, etc.)', which constitutes modification of existing data in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

testcase_update Rate-limited

testcase_update 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": {
    "testcase_update": {
      "limits": [
        {
          "counter": "testcase_update_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 Testops, so you can run agents against it safely.

FAQ

Questions about testcase_update

What does the testcase_update tool do? +

Update test case metadata (name, description, status, tags, etc.). Does NOT change steps or custom fields — use testcase_set_scenario / testcase_update_custom_fields for those. It is categorised as a Write tool in the Testops MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on testcase_update? +

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

What risk level is testcase_update? +

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

Can I rate-limit testcase_update? +

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

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

testcase_update is provided by the Testops MCP server (@syn7xx/testops-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.