browser_disconnect_proxy
Disable the proxy and revert to direct connection. Useful for comparing behavior with and without proxy, or troubleshooting connection issues.
When to use browser_disconnect_proxy
Use browser_disconnect_proxy when you need to route traffic through proxies or Tor for per-session IP isolation. It is part of Owl Browser's Proxy Management toolset and runs inside a self-hosted, source-level stealth engine, so every call inherits the same undetectable browser fingerprint as the rest of your automation — no separate anti-detect setup required.
Usage Example
Parameters
Required
context_idstringrequiredThe unique identifier of the browser context (e.g., 'ctx_000001')
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does browser_disconnect_proxy do?
Disable the proxy and revert to direct connection. Useful for comparing behavior with and without proxy, or troubleshooting connection issues. It belongs to Owl Browser's Proxy Management category and is available through the REST API, the Python SDK (browser.disconnect_proxy()), the Node.js SDK, and the MCP server.
What parameters does browser_disconnect_proxy accept?
browser_disconnect_proxy accepts 1 required parameter (context_id) and 0 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_disconnect_proxy.
Is browser_disconnect_proxy detectable by anti-bot systems like Cloudflare or DataDome?
No. browser_disconnect_proxy executes inside Owl Browser's Chromium engine, which applies fingerprint spoofing at the C++ source level rather than through JavaScript patches. Every tool call shares the same consistent, human-like fingerprint, so anti-bot systems such as Cloudflare, DataDome, and Akamai see an ordinary browser.
Related Tools
browser_set_proxyConfigure proxy settings for the browser context after creation. Supports HTTP, HTTPS, SOCKS4, SOCKS5, and SOCKS5H proxies with optional authentication. Includes stealth features to prevent proxy detection.
browser_get_proxy_statusGet the current proxy configuration and connection status. Returns proxy type, host, port, and whether stealth features are enabled.
browser_connect_proxyEnable and connect the configured proxy for the browser context. Traffic will start routing through the proxy after this call.
browser_create_contextCreate a new isolated browser context with its own cookies, storage, and optional proxy configuration. Each context acts as an independent browser session. Use this to create multiple isolated browsing sessions, configure proxy/Tor connections, load browser profiles with saved fingerprints, and enable/disable LLM features. Returns a context_id to use with other browser tools.
browser_navigateNavigate the browser to a specified URL. This is a non-blocking operation that starts navigation and returns immediately. Use browser_wait_for_network_idle or browser_wait_for_selector to wait for the page to fully load. Supports HTTP, HTTPS, file, and data URLs. When wait_until is set (load, networkidle, fullscroll, domcontentloaded) and the page declares WebMCP tools, the response includes a webmcp_tools array containing the full tool definitions (name, description, inputSchema). Use browser_webmcp_call_tool to execute any of these tools directly.
browser_observeAgent-native page observation. Returns the compacted OwlMark render (text-only structural view of the page), a handle table of interactive elements with stable tokens, page metadata, and a token estimate. Pass a handle token (e.g. 'b3') or 'pm:N' to browser_click/browser_type. Requires the context to be created with render_mode 'agent' or 'both'. ~20-100x fewer tokens than a screenshot for AI agent page understanding.