# update_test_case

Update a test case\

Agent View of the PolicyLayer registry record for `update_test_case`. HTML page: https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/update-test-case

## Facts

- Tool: `update_test_case`
- Server: Debugg AI MCP (`debugg-ai/debugg-ai-mcp`) — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp.md
- Homepage: https://github.com/debugg-ai/debugg-ai-mcp
- Risk category: Write (Medium risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Rate-limited

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "update_test_case",
    "arguments": {}
  }
}
```

## 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 own definition: "Tool name 'update_test_case' and description 'Update a test case' indicate modification of existing test data in a reversible manner."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Debugg AI MCP:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_test_case": {
      "limits": [
        {
          "counter": "update_test_case_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Debugg AI MCP (6)

- `delete_test_case` — Destructive — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/delete-test-case.md
- `delete_test_suite` — Destructive — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/delete-test-suite.md
- `run_test_suite` — Execute — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/run-test-suite.md
- `get_test_suite_results` — Read — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/get-test-suite-results.md
- `search_test_suites` — Read — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/search-test-suites.md
- `create_test_suite` — Write — https://policylayer.com/tools/debugg-ai-debugg-ai-mcp/create-test-suite.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=debugg-ai-debugg-ai-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/debugg-ai-debugg-ai-mcp