MCP Tool
nova.media_device_preferences_list
For media permissions, active use, and audit signals, an agent uses this public tool to handle the sensitive path "Device Preferences List". It keeps purpose, scope, user control, and sensitive data handling explicit.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Media Permissions & Active Use
- Effect
- sensitive
- Status
- Explained
- Path
- 57.16
Purpose
What this entry explains
What it does
nova.media_device_preferences_list
An agent uses this tool to handle the sensitive path "Device Preferences List". It belongs to media permissions, active use, and audit signals; agents should combine it with current discovery, target awareness, and the visible result.
Use when
- Use this entry when an agent needs to handle the sensitive path "Device Preferences List" for media permissions, active use, and audit signals.
- Use it to understand the public tool name, its expected boundary, and the response signals to check.
- Use it before chaining follow-up tools so the next step is based on current evidence.
Reference Use
How agents should cite and apply this area
Examples are maintained at family level and use only public tool names or reference paths already present in the catalog.
Family example
A task in media permissions, active use, and audit signals can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with nova.tools_bundle, reads the current response or reference, and only then chooses the concrete next tool.
Current discovery, target, user control, warning signals, and result check come before execution.Contract
Inputs and important response fields
This page is a public reference. Agents and integrators should still read current MCP tool discovery before execution, because schemas can be gated by settings or version.
Inputs
origin
Origin value for site-scoped permissions and data.
| Response field | Explanation |
|---|---|
updatedUtc | Response field named by the catalog source. Treat it as current evidence for the next decision. |
Safety
Boundary before execution
May touch sensitive data, permissions, credentials, identity, or external connection paths. Use only with explicit scope and visible user control.
Require explicit purpose and current context, avoid exposing secrets in prompts or logs, and stop when permission or identity state is unclear.
For humans, this entry marks the sensitive surface in media permissions, active use, and audit signals and keeps permission, credential, or external-connection handling explicit.
High-Impact Review
Execution boundary and recheck hints
Review category: Recording/screenshots/media
Capture only the needed visual or media evidence and respect private content, recording state, and export boundary.
False assumption: screenshots or recordings contain only technical evidence.
Recording, screenshot, media access, or export must be visible to the user and purpose-bound.
Before capture, check target, scope, and privacy; use artifacts as evidence only and do not forward them unrequested.
Abort if private content is visible, media permission is unclear, or the export contains more than needed.
Safety Axes
How this path can affect work
Axes are stable catalog signals for humans, agents, and LLM discovery. One path can carry several axes.
read_current_state
Reads current state, response signals, or evidence without treating that alone as permission for a follow-up action.
Use the signal as current evidence and re-check target, scope, and visible state before any follow-up action.browser_state_change
Changes tab, navigation, focus, claim, scroll position, window state, or browser environment.
Confirm the target context visibly before execution and verify that the expected browser state was reached afterwards.sensitive_data
Touches cookies, storage, clipboard, credentials, tokens, user content, identity, or private data.
Use only with bounded purpose and visible user control; do not guess, log, or forward sensitive values.recording_or_media
Creates or reads screenshots, recordings, media, visual evidence, or audio/video signals.
Capture only needed evidence, respect private content, and keep media or recording state visible.user_confirmation
Requires visible confirmation, target review, approval, or deliberate user control.
Do not proceed until the required confirmation is visible or unambiguous in the current context.