testmo_update_case · Testmo MCP: Risk & Policy

WHAT IT DOES

What testmo_update_case does on Testmo

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

WHY IT NEEDS A POLICY

Why testmo_update_case needs a policy

The tool updates (modifies) existing test case records in Testmo, which is a reversible Write operation. No description provided limits confidence slightly, but the naming convention and server context make the intent clear. Severity is medium because unintended case updates could corrupt test data and impact CI/CD pipelines, but changes are typically reversible via subsequent updates.

From the tool's definition Tool name 'testmo_update_case' indicates modification of test case data. Server description confirms it 'manage[s] test cases' and the presence of sibling tools like 'testmo_batch_update_cases' and 'testmo_create_case' establishes this as a data modification…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

testmo_update_case Rate-limited

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

FAQ

Questions about testmo_update_case

What does the testmo_update_case tool do? +

testmo_update_case. It is categorised as a Write tool in the Testmo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on testmo_update_case? +

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

What risk level is testmo_update_case? +

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

Can I rate-limit testmo_update_case? +

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

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

testmo_update_case is provided by the Testmo MCP server (strelec00/testmo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.