Permissions-Policy introspection and reporting
A page can list which browser features it is allowed to use, and a server can hear about violations.
document.permissionsPolicy.features() returns every feature the browser knows, and allowedFeatures() the ones this frame may use. Permissions-Policy-Report-Only lets a server learn what a page would break. Feature-Policy is the legacy name.
What it can and can't do
What the user does: None, the page reads it silently
It can
- List all policy controlled features in Chromium
- Tell which features a frame may use
- Report violations to a server
It cannot
- Change a policy from script
- See other frames' policy
How it differs between platforms: Chromium implements it. Safari and Firefox are partial or absent. Report only and Document-Policy are low confidence.
Browser support
Version notes
- Chrome: Introspection API and report only header
- Edge: Same as Chrome
- Firefox: Header support is partial per caniuse
- Safari: Header support is partial per caniuse
- Safari on iPhone: Same as Safari
- Chrome on Android: Same as Chrome
How a site asks for it
| API | document.permissionsPolicy.features(); document.permissionsPolicy.allowedFeatures(); allowsFeature(name); Permissions-Policy-Report-Only |
| Browser compat keys | api.PermissionsPolicyhttp.headers.Permissions-Policy |
| How access is granted | none |
| What the user sees | None |
| Needs a secure context (HTTPS) | Yes |
| Needs a user gesture | No |
| How long it lasts | Per origin |
| How to take it back | Clear site data |
| Inside an iframe | Same as top level |
Typical flow
- Page calls the API
- Browser answers with no prompt
- Page reads the result
Data you get
What comes back: A page can list which browser features it is allowed to use, and a server can hear about violations.
Shape: object
How often: on demand
| Field | Type | Unit | Range | Precision |
|---|---|---|---|---|
features() | list | None | every policy controlled feature | Not listed |
allowedFeatures() | list | None | features this frame may use | Not listed |
report only | header | None | violation reports to the server | Not listed |
Technical limits
- Chromium centered
- Document-Policy and Feature-Policy details are low confidence
- Report only is low confidence
The story
What it is
The page can read the rule list that decides which browser powers its frames may use.
For you
This is about what a page and the ads in it are allowed to do. You rarely see it.
For makers
Makers lock down embedded frames and check their own policy at run time.
Where you see it
| Type | Example | Apps |
|---|---|---|
| shopping | A shop blocks camera and microphone access for embedded ads. | None named |
| news | A publisher checks which features its ad frames may use. | None named |
Risks
- The feature list is itself a browser version signal
What the platform says
- W3C: Permissions Policy. The standard for controlling which features a page and its frames can use.
Good uses and abuse
Legitimate uses
- Harden frames
- Debug policy
Known abuse
- Browser version fingerprinting
Scores
| Score | Value | Meaning |
|---|---|---|
| Sensitivity | 1 of 5 | How revealing the data is |
| Utility | 3 of 5 | How useful it is to honest apps |
| Friction | 0 of 5 | How much the user has to do |
| Fingerprint bits | 1 | Rough identifying entropy, when known |
Related capabilities
Related
- Permissions Policy and iframe allow. Can turn features off for itself and its embedded frames
- Permissions API. Can check whether you allowed or blocked a feature, without asking you
Sources
- W3C Permissions Policy (checked 2026-11-16)
- MDN Permissions-Policy header (checked 2026-11-16)
- MDN Permissions-Policy-Report-Only (checked 2026-11-16)
How well checked: Inferred from related behavior.