uat_claim_test · Local Dev Bridge MCP: Risk & Policy

WHAT IT DOES

What uat_claim_test does on Local Dev Bridge MCP

AI agents use uat_claim_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_claim_test needs a policy

This tool moves a test record from one state/directory to another (pending → in-progress), which is a reversible state change/write operation. It does not execute code, delete data, or involve finances. The blast radius is moderate — misuse could lock or incorrectly claim tests, disrupting test workflows, but the action is reversible.

From the tool's definition 'Claim a pending test for execution. Moves it from pending/ to in-progress/'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

uat_claim_test Rate-limited

uat_claim_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_claim_test": {
      "limits": [
        {
          "counter": "uat_claim_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_claim_test

What does the uat_claim_test tool do? +

Claim a pending test for execution. Moves it from pending/ to in-progress/ so other sessions don\. 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_claim_test? +

Register the Local Dev Bridge MCP server in PolicyLayer and add a rule for uat_claim_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_claim_test? +

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

Can I rate-limit uat_claim_test? +

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

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

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