Add chrome policy use case for blocking DevTools - #466
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
dprevoznik
marked this pull request as ready for review
July 29, 2026 00:45
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a Block DevTools and page source use case to the custom Chrome policies page, showing how to block
devtools://*,chrome://inspect, andview-source:*withURLBlocklist.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.