testcase_set_scenario · Testops MCP: Risk & Policy

WHAT IT DOES

What testcase_set_scenario does on Testops

AI agents use testcase_set_scenario 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_set_scenario needs a policy

This tool modifies test case scenarios by replacing steps, which constitutes data modification (Write category). The severity is medium because: (1) the change is reversible (can be undone by replacing again), (2) it affects test data rather than production systems, and (3) the blast radius is limited to test automation artifacts.

From the tool's definition Tool name 'testcase_set_scenario' and description 'Replace all steps in a test case scenario' indicate modification of test case data. The verb 'set' and 'replace' show data is being overwritten, which is a Write operation (reversible modification).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

testcase_set_scenario Rate-limited

testcase_set_scenario 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_set_scenario": {
      "limits": [
        {
          "counter": "testcase_set_scenario_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_set_scenario

What does the testcase_set_scenario tool do? +

Replace all steps in a test case scenario. 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_set_scenario? +

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

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

Can I rate-limit testcase_set_scenario? +

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

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

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