uat_complete_test · Local Dev Bridge MCP: Risk & Policy

WHAT IT DOES

What uat_complete_test does on Local Dev Bridge MCP

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

WHY IT NEEDS A POLICY

Why uat_complete_test needs a policy

This tool creates or modifies data (test results) and moves files between directories (in-progress/ to results/), which are reversible write operations. While it involves file system modifications, it is not destructive since the original data is preserved in the results directory and the operation can be undone.

From the tool's definition Mark a test as completed with results. Moves it from in-progress/ to results/ and writes the outcome.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

uat_complete_test Rate-limited

uat_complete_test 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": {
    "uat_complete_test": {
      "limits": [
        {
          "counter": "uat_complete_test_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 Local Dev Bridge MCP, so you can run agents against it safely.

FAQ

Questions about uat_complete_test

What does the uat_complete_test tool do? +

Mark a test as completed with results. Moves it from in-progress/ to results/ and writes the outcome. Use this after executing a test in the browser. It is categorised as a Write tool in the Local Dev Bridge 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 uat_complete_test? +

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

What risk level is uat_complete_test? +

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

Can I rate-limit uat_complete_test? +

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

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

uat_complete_test is provided by the Local Dev Bridge MCP server (talentedmrweb/local-dev-bridge-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.