browser_enable_network_logging
Enable or disable network request/response logging for the context. When enabled, all network activity is captured and can be retrieved with get_network_log.
When to use browser_enable_network_logging
Use browser_enable_network_logging when you need to intercept, block, mock, or monitor network requests. It is part of Owl Browser's Network Interception 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')
Optional
enablebooleanEnable (true) or disable (false) network logging for this context. One of 'enable' or 'enabled' is required.
enabledbooleanAlias for 'enable'. Accepted interchangeably; if both are given, 'enable' wins.
Response
Returns a JSON object with the operation result.
{
"success": true,
"result": <value>
}Frequently Asked Questions
What does browser_enable_network_logging do?
Enable or disable network request/response logging for the context. When enabled, all network activity is captured and can be retrieved with get_network_log. It belongs to Owl Browser's Network Interception category and is available through the REST API, the Python SDK (browser.enable_network_logging()), the Node.js SDK, and the MCP server.
What parameters does browser_enable_network_logging accept?
browser_enable_network_logging accepts 1 required parameter (context_id) and 2 optional parameters. All parameters are sent as JSON in a POST request to /api/execute/browser_enable_network_logging.
Is browser_enable_network_logging detectable by anti-bot systems like Cloudflare or DataDome?
No. browser_enable_network_logging 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_get_headersGet HTTP response headers from the current page or a specific URL in the browser context. Network logging is automatically enabled when a context is created. Returns headers as a JSON object with header names as keys. Useful for extracting authentication tokens, content types, caching directives, and other response metadata.
browser_add_network_ruleAdd a rule to intercept network requests matching a URL pattern. Rules can block requests (e.g., ads, trackers), mock responses with custom data (useful for testing), or redirect to different URLs. Supports glob patterns (*.js, *://api.example.com/*) or regex for flexible matching. Returns a rule_id for later removal.
browser_remove_network_ruleRemove a previously added network interception rule by its ID. The rule immediately stops applying to new requests. Use browser_add_network_rule's returned rule_id to remove specific rules.
browser_enable_network_interceptionEnable or disable network interception for a context. When disabled, all rules are ignored and requests pass through normally. When enabled, rules start applying. Useful for toggling interception without removing rules.
browser_get_network_logRetrieve the log of captured network requests and responses for debugging and analysis. Returns request URLs, methods, headers, status codes, and response sizes. Enable interception first to start capturing.
browser_get_network_rulesList all network interception rules for a context. Returns an array of rules with their id, url_pattern, action (block/allow/mock/redirect), is_regex flag, and additional settings like redirect_url or mock_body depending on the action type.