updateTestCase · BrowserStack MCP: Risk & Policy

WHAT IT DOES

What updateTestCase does on BrowserStack

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

WHY IT NEEDS A POLICY

Why updateTestCase needs a policy

This tool modifies test case metadata and configuration data in a test management system. Updates are reversible—previous versions can typically be restored or the changes reverted through subsequent calls.

From the tool's definition Tool description explicitly states it can 'Update an existing test case' with modifiable fields including name, description, preconditions, test_case_steps, owner, priority, case_type, automation_status, status, tags, issues, and custom_fields.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

updateTestCase Rate-limited

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

FAQ

Questions about updateTestCase

What does the updateTestCase tool do? +

Update an existing test case in BrowserStack Test Management. Any subset of the following fields may be changed: name, description, preconditions, test_case_steps, owner, priority, case_type, automation_status, status, tags, issues, custom_fields. Only the supplied fields are modified. It is categorised as a Write tool in the BrowserStack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on updateTestCase? +

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

What risk level is updateTestCase? +

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

Can I rate-limit updateTestCase? +

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

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

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