Browser-use blocks an explicitly authorized, user-owned Naver Blog page

Summary

In the Codex desktop app on Windows, browser-use refused to inspect a public Naver Blog post that was already open in the right-side browser, even after the user explicitly authorized access and stated that they own the blog and its content.

Target URL:
https://m.blog.naver.com/jimin2mam/224396560040?referrerCode=1

Steps to reproduce

1. Open the public Naver Blog post in Codex's right-side in-app browser (the same page was also open in Chrome).
2. Ask Codex to read the post text and original images in order to create a promotional YouTube Short.
3. Explicitly confirm that the user owns the blog/content and authorizes its use.
4. Attempt to inspect the page with browser-use.

Actual behavior

The browser tool returned:

Browser use is not permitted on https://m.blog.naver.com/jimin2mam/224396560040

It also instructed the agent not to obtain the same content through another browser surface, CDP, Playwright, screenshots, or other workarounds. The agent complied and did not bypass the restriction.

Expected behavior

Codex should be able to inspect the text and images of a public page that the user has opened and explicitly authorized, or provide a clear, actionable explanation identifying whether the denial comes from a site permission, organization policy, or safety classification.

Additional checks

• Chrome DevTools MCP 1.8.0 initialized successfully and returned its tool list; this did not change the denial.
• Any custom URL-specific block rule added during troubleshooting was removed.
• No article body text or original images were obtained after the refusal.
• No passwords, cookies, authentication tokens, phone numbers, or full session logs are included in this report.

Request

Please review whether this is a false-positive site-safety denial and document a supported way to restore access without broadly disabling security controls.

Start with the browser-use decision for the provided Naver Blog URL, considering the explicit ownership authorization and the removed custom URL rule. Check whether the denial can identify a site permission, organization policy, or safety classification; done means documenting the cause and a supported restoration path without broadly disabling security controls.