update_test_case

Update a test case\

SERVERDebugg AI MCP SOURCEdebugg-ai/debugg-ai-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/debugg-ai-debugg-ai-mcp/update-test-case.md

WHAT IT DOES

What update_test_case does on Debugg AI MCP

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

RISK

Why update_test_case is rated Medium

This tool modifies test case data, which is a Write operation. The sibling tools include destructive operations (delete_test_case, delete_test_suite) and read operations (get_test_suite_results, search_test_suites), confirming this server manages test lifecycle. Updating test cases is reversible and does not irreversibly delete data, run external code, or move funds.

From the tool's definition Tool name 'update_test_case' and description 'Update a test case' indicate modification of existing test data in a reversible manner.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_test_case safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Debugg AI MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_test_case, this is the rule to start with:

update_test_case Rate-limited

update_test_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": {
    "update_test_case": {
      "limits": [
        {
          "counter": "update_test_case_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Debugg AI MCP, apply this rule, and every update_test_case call is checked against it from then on.

FAQ

Questions about update_test_case

What does the update_test_case tool do? +

Update a test case\. It is categorised as a Write tool in the Debugg AI MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_test_case? +

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

What risk level is update_test_case? +

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

Can I rate-limit update_test_case? +

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

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

update_test_case is provided by the Debugg AI MCP server (debugg-ai/debugg-ai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Debugg AI, and thousands of servers like it.

This server

All 7 Debugg AI tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →