ui_network_requests
AI agents call ui_network_requests 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.
Based on the naming pattern and server purpose (inspect and interact with UI elements), this tool most likely reads/retrieves network request data for inspection purposes. No evidence suggests it creates, executes, deletes, or transfers money. The empty description reduces confidence slightly, but the preponderance of read-like sibling tools supports a Read classification.
From the tool's definition Tool name 'ui_network_requests' suggests querying or inspecting network requests made by the UI. The description is empty, but context from sibling tools (diagnose_stuck_screen, get_idle_status, sdk_ai_search, sdk_analyze_*) indicates this server primarily…
Attacks that exploit this kind of access
ui_network_requests. 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_network_requests: 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_network_requests 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_network_requests 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_network_requests. 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_network_requests 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 →