testmo_batch_update_cases · Testmo MCP: Risk & Policy

WHAT IT DOES

What testmo_batch_update_cases does on Testmo

AI agents use testmo_batch_update_cases 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_batch_update_cases needs a policy

The tool updates (modifies) test case data in batch, which is a Write operation—reversible changes to existing records. While the description is empty, the name and context of similar tools on the Testmo test management server clearly indicate data modification without deletion. Severity is medium because batch updates could affect multiple records, but changes are reversible.

From the tool's definition Tool name 'testmo_batch_update_cases' indicates it modifies multiple test cases in batch. The verb 'update' and 'batch' prefix show reversible data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

testmo_batch_update_cases Rate-limited

testmo_batch_update_cases 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_batch_update_cases": {
      "limits": [
        {
          "counter": "testmo_batch_update_cases_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_batch_update_cases

What does the testmo_batch_update_cases tool do? +

testmo_batch_update_cases. 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_batch_update_cases? +

Register the Testmo MCP server in PolicyLayer and add a rule for testmo_batch_update_cases: 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_batch_update_cases? +

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

Can I rate-limit testmo_batch_update_cases? +

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

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

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