Tested this issue on GPO Test environment(Windows)

Preconditions:
1. Enabled the "Disable devtools policy"
2. Updated the policy in client machine and launched chrome with --remote-debugging-port=9222


Steps Followed:
1. Confirm the devtools are disabled
2. Navigate to test url like "https://duckduckgo.com"
3. In the new tab navigate to "localhost:9222"
4. Click on the url

Observations:
I was able to inspect the test url

Attaching the screen-cast for reference.

dpapad@ Could you confirm this is the issue you are facing???

Deleted: 822088.mp4 2.2 MB

	822088.mp4 2.2 MB View Download

@kkaluri: No these are not the steps I followed and described originally.

> 3. In the new tab navigate to "localhost:9222"
> 4. Click on the url

Step 3 is not what I did. Need to go to a new chrome instance (different user-data-dir, and ensure that the policy is not applied for that instance). This can be either on the same or on a different computer entirely.
Step 4: Go to chrome://inspect, not localhost:9222.

I don't know if the steps described here are equivalent to the bug I am observing.

This is interesting question - whether remote dev tools should be disabled when the policy is in effect. It sounds to me like they should but let's broadcast the question more widely.

Blumberg - you have an opinion here? Not really a cros issue because you have to be in dev mode to enable remote debugging at which point all policies are moot.

+privard for his input as well.

I think that request makes sense. Could we envision a scenario where an admin would like to disable dev tools but keep the remote (maybe there is a valid usecase for that?). In which case, maybe a separate policy for the remote debugging is more appropriate.