List all pending UAT tests waiting to be executed. Use this from the browser-side session to see what needs testing.
AI agents call uat_get_pending 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 retrieves and displays information about pending tests without modifying state, executing code, or causing irreversible changes. It is a read-only operation that simply queries test status. The low severity reflects minimal blast radius if misused—an agent could see what tests exist, but cannot execute them, modify them, or affect other systems.
From the tool's definition Tool name 'uat_get_pending' and description 'List all pending UAT tests waiting to be executed' indicate a query/retrieval operation with no data modification or execution side effects.
Attacks that exploit this kind of access
List all pending UAT tests waiting to be executed. Use this from the browser-side session to see what needs testing. 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_pending: 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_pending 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_pending 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_pending. 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_pending 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 →