sdk_elements
AI agents call sdk_elements 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 tool likely retrieves UI element information for inspection or analysis (evidenced by sibling analysis and search tools), which is a Read operation with no side effects. However, confidence is reduced because the description is empty and the exact function cannot be verified. If this tool were to execute UI interactions like clicks or inputs, it would be reclassified as Execute.
From the tool's definition Tool name 'sdk_elements' combined with sibling tools named 'sdk_ai_search', 'sdk_analyze_*', and 'sdk_annotated_screenshot' suggests data inspection/querying capability. The 'SDK' prefix indicates introspection of external application elements.
Attacks that exploit this kind of access
sdk_elements. 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_elements: 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_elements 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_elements 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_elements. 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_elements 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 →