testcase_update_custom_fields · Testops MCP: Risk & Policy

WHAT IT DOES

What testcase_update_custom_fields does on Testops

AI agents use testcase_update_custom_fields 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_custom_fields needs a policy

This tool creates or modifies data reversibly by updating custom field values. It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), and has no financial implications. The blast radius is moderate—an agent could inadvertently corrupt test metadata or custom field data, but the change is reversible via another update operation.

From the tool's definition Tool name contains 'update' and description states 'Update custom field values for a test case', which modifies data on an existing test case.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

testcase_update_custom_fields Rate-limited

testcase_update_custom_fields 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_custom_fields": {
      "limits": [
        {
          "counter": "testcase_update_custom_fields_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_custom_fields

What does the testcase_update_custom_fields tool do? +

Update custom field values for a test case. 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_custom_fields? +

Register the Testops MCP server in PolicyLayer and add a rule for testcase_update_custom_fields: 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_custom_fields? +

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

Can I rate-limit testcase_update_custom_fields? +

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

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

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