Get a summary dashboard of the UAT queue — counts of pending, in-progress, and completed tests broken down by status and priority.
AI agents call uat_dashboard 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.
uat_dashboard performs a query operation that retrieves aggregated test status data without creating, modifying, deleting, or executing any operations. This is a pure Read operation with minimal blast radius if misused by an AI agent.
From the tool's definition The tool description explicitly states it 'Get[s] a summary dashboard' and 'counts of pending, in-progress, and completed tests' — read-only retrieval of status information with no side effects.
Attacks that exploit this kind of access
Get a summary dashboard of the UAT queue — counts of pending, in-progress, and completed tests broken down by status and priority. 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_dashboard: 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_dashboard 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_dashboard 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_dashboard. 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_dashboard 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 →