Add chrome policy use case for blocking DevTools

[dprevoznik]

Summary

Adds a Block DevTools and page source use case to the custom Chrome policies page, showing how to block devtools://*, chrome://inspect, and view-source:* with URLBlocklist.

Verification

Confirmed the policy behaves as documented on a live browser session: all three URLs fail with net::ERR_BLOCKED_BY_ADMINISTRATOR, F12 in live view shows "Your organization has blocked the use of DevTools on this page", and Playwright over CDP still drives the session.

Docs-only change, no tests to run.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Error		Jul 29, 2026 12:47am

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Jul 29, 2026, 12:45 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

[cursor]

Risk assessment: Very Low

Verdict: Risk unchanged after update. Prior approval stands; not re-approving.

Evidence (from diff only)

• 1 file changed:browsers/pools/policy-json.mdx (+30 / −0 vs base)
• Change type: Documentation-only — adds a “Block DevTools and page source” use-case section with Python and TypeScript examples using existing chrome_policy / URLBlocklist
• Post-approval delta (7083036 → ed7884d): removes 4 lines of explanatory prose only; no new files, code, APIs, auth, infra, or schema
• No application/runtime behavior changes in this repo
• Small surface; blast radius limited to published docs copy/examples

Re-approval check

This automation previously approved at 7083036 as Very Low. The synchronize update does not increase risk, so approval is retained and not dismissed.

Decision

Very Low → comment only (already approved). No CODEOWNERS requirement detected.

_{Sent by Cursor Automation: Assign PR reviewers}