Get test results. Use this from Claude Code to check how tests went after the browser session ran them.
AI agents call uat_get_results to retrieve information from Local Dev Bridge MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and retrieves test results that have already been generated. It performs no modifications, deletions, code execution, or financial operations. The retrieval of test results is a standard Read operation with minimal risk - the worst case is information disclosure about test outcomes, which has low blast radius in a development environment.
From the tool's definition Tool description states 'Get test results' and 'check how tests went' - these are retrieval operations with no side effects. The verb is 'Get' and the action is to retrieve and display existing test result data.
Attacks that exploit this kind of access
Get test results. Use this from Claude Code to check how tests went after the browser session ran them. It is categorised as a Read tool in the Local Dev Bridge MCP MCP Server, which means it retrieves data without modifying state.
Register the Local Dev Bridge MCP server in PolicyLayer and add a rule for uat_get_results: 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.
uat_get_results is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the uat_get_results 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.
Set action: deny in the PolicyLayer policy for uat_get_results. 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.
uat_get_results 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →