sdk_design_diff
AI agents call sdk_design_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.
The 'sdk_' prefix and 'diff' naming pattern strongly suggest this compares UI design states or screenshots without modifying data. No verb like 'execute', 'delete', or 'modify' is present. The empty description lowers confidence slightly, but the sibling tools (sdk_ai_search, sdk_analyze_data, sdk_analyze_regions) are all read/analysis operations, suggesting a consistent pattern.
From the tool's definition Tool name 'sdk_design_diff' suggests a comparison/diffing operation; no description provided, but naming convention and context within UI Bridge MCP's inspection capabilities indicate this is a read-only analysis tool.
Attacks that exploit this kind of access
sdk_design_diff. 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 sdk_design_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.
sdk_design_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 sdk_design_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 sdk_design_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.
sdk_design_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 →