MCP Tool

`nova.scheduled_task_disable`

For prepared tasks, runs, and closed-loop automation steps, an agent uses this public tool to start or monitor the bounded flow "Task deaktivieren". It names the scope, progress signal, stopping condition, and result check that keep the run bounded.

Agent tool

Canonical reference for a public MCP tool name.

Type: MCP tool
Family: Scheduled Tasks
Effect: bounded run
Status: Explained
Path: 17.7

Purpose

What this entry explains

What it does

nova.scheduled_task_disable An agent uses this tool to start or monitor the bounded flow "Task deaktivieren". It belongs to prepared tasks, runs, and closed-loop automation steps; agents should combine it with current discovery, target awareness, and the visible result.

Use when

Use this entry when an agent needs to start or monitor the bounded flow "Task deaktivieren" for prepared tasks, runs, and closed-loop automation steps.
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 prepared tasks, runs, and closed-loop automation steps can trigger powerful execution and therefore needs target, approval, and result check before the step.

The agent starts with nova.scheduled_task_create, reads the current response or reference, and only then chooses the concrete next tool.

nova.scheduled_task_create nova.scheduled_task_list nova.scheduled_task_trigger

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

taskId

Task reference for a scheduled or stored work context.

Response fields

No fixed public response field is derived from the catalog source for this path. Use current tool discovery and the actual response before chaining the next step.

Safety

Boundary before execution

Effect

Starts or observes a bounded run. Scope, limits, progress, and terminal status need to stay visible.

Agent rule

Set scope and limits before starting the run, poll explicit progress or status fields, and stop instead of assuming completion.

Human control

For humans, this entry shows which bounded flow in prepared tasks, runs, and closed-loop automation steps starts or continues, and where scope, progress, and stopping conditions belong.

High-Impact Review

Execution boundary and recheck hints

Review category: Scheduler/tasks/automation

Execution boundary

Runs need scope, budget, progress, stop condition, and reviewable terminal status before they start or continue.

Typical false assumption

False assumption: once started, a run may continue until success.

Visible user control

Task, schedule, variables, workspace, and run status must remain reviewable by the user.

Agent rule

Bound automations, poll progress, check terminal status, and avoid chaining when results are unclear.

Abort or recheck

Abort or recheck when budget, target set, run ID, workspace, or result status becomes unclear.

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.

Persistent persistent_change

Saves, deletes, remembers, schedules, or changes data that may outlive the immediate page state.

Execute only with clear scope and keep the saved, deleted, or scheduled effect reviewable.

Automation automation_run

Starts or monitors crawls, sequences, schedulers, tasks, batches, or longer runs.

Keep scope, budget, progress, stop condition, and terminal status visible before and during the run.

High-impact execution high_impact_execution

Runs or prepares JavaScript, CDP, plugin code, auto-apply, or other powerful execution paths.

Explicitly confirm current tool discovery, target, scope, user control, and result check before execution.

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.

nova.scheduled_task_disable