Get a budget-aware text summary of runner UI changes (Control mode).
AI agents call ui_summarize_diff to retrieve information from UI 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 summarizes information about UI state changes without creating, modifying, deleting, or executing external operations. It is purely observational and informational, making it a Read category tool with low severity since misuse would only result in information disclosure or wasted budget on summary generation.
From the tool's definition Tool description states it 'Get[s] a... text summary' of UI changes. The verb 'get' and 'summarize' indicate data retrieval with no modification. 'Control mode' operates on the runner's own UI without external effects.
Attacks that exploit this kind of access
Get a budget-aware text summary of runner UI changes (Control mode). It is categorised as a Read tool in the UI Bridge MCP MCP Server, which means it retrieves data without modifying state.
Register the UI Bridge MCP server in PolicyLayer and add a rule for ui_summarize_diff: 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 UI Bridge MCP. Nothing to install.
ui_summarize_diff 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 ui_summarize_diff 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 ui_summarize_diff. 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.
ui_summarize_diff is provided by the UI Bridge MCP server (qontinui/ui-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 →