sdk_network_requests
AI agents call sdk_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.
Network request inspection is primarily a Read operation—it queries or observes data about network communications without modifying them. Severity is medium because exposed network monitoring could leak sensitive data (credentials, API keys, request payloads) if misused by an AI agent, but it does not execute code, delete data, or trigger financial transactions.
From the tool's definition Tool name 'sdk_network_requests' suggests observation/inspection of network activity; broader UI Bridge MCP context emphasizes inspection ('inspect and interact with UI elements'). The empty description weakens confidence.
Attacks that exploit this kind of access
sdk_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 sdk_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.
sdk_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 sdk_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 sdk_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.
sdk_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 →