MCP Path

ScreenCapture/Geolocation Achsen

ScreenCapture/Geolocation Achsen is a public reference for media permissions, active use, and audit signals. It names the signal, policy, or flow an agent should understand before choosing a concrete tool.

Catalog path

Reference page for a documented MCP capability path.

Type: MCP path
Family: Media Permissions & Active Use
Effect: sensitive
Status: Reference
Path: 57.6

Purpose

What this entry explains

What it does

This reference explains ScreenCapture/Geolocation Achsen for media permissions, active use, and audit signals. It is kept as a named reference so agents can cite the flow without inventing a tool name.

Use when

Use this entry when an agent needs to handle the sensitive path "ScreenCapture/Geolocation Achsen" for media permissions, active use, and audit signals.
Use it as a reference path when the catalog describes a capability but no single public tool name is explicit.
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.

Signal, gate, behavior, boundary

ScreenCapture/Geolocation Achsen describes a gate for media permissions, active use, and audit signals. The path shows which signal, gate, behavior, or boundary must be checked before choosing a concrete tool.

When agents cite it

An agent cites this path when it needs ScreenCapture/Geolocation Achsen as context for a decision, block, target check, or follow-up tool choice.

Why no callable name

The public source does not name one callable tool for this path. The documentation therefore keeps it as a reference path and does not invent a callable name.

Signals and rule

Relevant response signals: screenCapture. Safety axes: Browser state, Sensitive, Recording / media, User confirmation. The reference path alone is not permission to execute. Before acting, check current MCP discovery, visible target, scope, and the actual response.

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.

nova.tools_bundle nova.media_permissions_list nova.media_permission_set

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

No stable public input field is derived from the catalog source for this path. Read current MCP discovery before execution.

Response field	Explanation
`screenCapture`	Response field named by the catalog source. Treat it as current evidence for the next decision.

Safety

Boundary before execution

Effect

May touch sensitive data, permissions, credentials, identity, or external connection paths. Use only with explicit scope and visible user control.

Agent rule

Require explicit purpose and current context, avoid exposing secrets in prompts or logs, and stop when permission or identity state is unclear.

Human control

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

Execution boundary

Capture only the needed visual or media evidence and respect private content, recording state, and export boundary.

Typical false assumption

False assumption: screenshots or recordings contain only technical evidence.

Visible user control

Recording, screenshot, media access, or export must be visible to the user and purpose-bound.

Agent rule

Before capture, check target, scope, and privacy; use artifacts as evidence only and do not forward them unrequested.

Abort or recheck

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.

Browser state 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 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 / media 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 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.