MCP Tool
nova.session_record_events
For recordings, event streams, and reviewable evidence, an agent uses this public tool to handle the sensitive path "V2 Sidecar Stream Enum". It keeps purpose, scope, user control, and sensitive data handling explicit.
Canonical reference for a public MCP tool name.
- Type
- MCP tool
- Family
- Session Recording
- Effect
- sensitive
- Status
- Explained
- Path
- 58.22
Purpose
What this entry explains
What it does
nova.session_record_events
An agent uses this tool to handle the sensitive path "V2 Sidecar Stream Enum". It belongs to recordings, event streams, and reviewable evidence; 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 "V2 Sidecar Stream Enum" for recordings, event streams, and reviewable evidence.
- 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 recordings, event streams, and reviewable evidence can trigger powerful execution and therefore needs target, approval, and result check before the step.
The agent starts with tools/list, 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
No stable public input field is derived from the catalog source for this path. Read current MCP discovery before execution.
| Response field | Explanation |
|---|---|
permission_revoked | Decision or block signal. It explains why the current step should continue, pause, or stop. |
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 recordings, event streams, and reviewable evidence and keeps permission, credential, or external-connection handling explicit.
High-Impact Review
Execution boundary and recheck hints
Review category: Plugin runtime
Plugin code and runtime calls stay limited to explicitly approved tools, permissions, and target contexts.
False assumption: an installed or loaded plugin may use all available browser data.
Approval, active tab, permission, and test result must remain visible user controls.
Execute plugin capabilities only after current tool discovery and permission checks; do not blindly chain external runtime output.
Recheck when permissions are missing, a plugin is unknown, or runtime status diverges from expected scope.
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.
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.