create_task

SERVERYaver SOURCEyaver-cli

High RISK CLASS

Category Execute

Parameters 101 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/create-task.md

WHAT IT DOES

What create_task does on Yaver

AI agents invoke create_task to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Parameter	Type	Required	Description
`goal`	string	—	Yaver goal-mode objective (opencode goal plugin). When set, the task runs as a persistent goal the opencode runner keeps working toward across turns (create_goa
`mode`	string	—	Runner-specific subcommand. Currently honored by opencode where it maps to `--agent <mode>` — typically 'build' or 'plan', or any custom agent defined in the us
`model`	string	—	Model id forwarded to the runner (e.g. claude-opus-4-8, gpt-5.6-sol, or any opencode-configured provider/model). Empty = Convex-backed Yaver default.
`prompt`	string	Yes	The task prompt describing what the AI should do
`runner`	string	—	Runner ID — claude / codex / opencode. Empty = agent default.
`ask_mode`	boolean	—	Default false. When true, the task runs as a grounded deep question-answer (askModePreamble: file:line citations, explain-first, confirm gate) instead of a work
`device_id`	string	—	Optional owned Yaver device id/name/alias to create the task on. Empty runs on the local MCP host.
`ask_freely`	boolean	—	Default false. When true, the new task is exempt from yaver's no-questions preamble + soft-question fallback — the runner may emit clarifying questions in prose
`video_source`	string	—	Override the auto-detected recorder. Empty = let the agent infer from the task's workDir (e.g. RN/Expo with ios/ → sim-ios; web → browser).
`video_enabled`	boolean	—	Toggle the post-completion video summary. When true, after the task finishes the agent records a short MP4 demonstrating the running result via vibe-preview (si

Parameters from the server's own tool schema.

RISK

Why create_task is rated High

Executes coding tasks on local or remote machines, triggering arbitrary code execution.

From the tool's definition Create a new coding task... runs on this agent's machine

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs create_task safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create_task, this is the rule to start with:

create_task Rate-limited

create_task stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_task": {
      "limits": [
        {
          "counter": "create_task_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every create_task call is checked against it from then on.

FAQ

Questions about create_task

What does the create_task tool do? +

Create a new coding task. By default it runs on this agent's machine; pass device_id to run it on another owned Yaver machine over the same relay/direct device routing used by the CLI. Returns a structured task object when accepted; when video recording is enabled and a clip exists, the task includes videoClipId/videoStatus/videoClipUrl/videoPosterUrl so MCP clients can render a watch link or inline player for demos recorded on the producing machine. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does create_task accept? +

create_task accepts 10 parameters: goal, mode, model, prompt, runner, ask_mode, device_id, ask_freely, video_source, video_enabled. Required: prompt. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on create_task? +

Register the Yaver MCP server in PolicyLayer and add a rule for create_task: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Yaver. Nothing to install.

What risk level is create_task? +

create_task is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_task? +

Yes. Add a rate_limit block to the create_task rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block create_task completely? +

Set action: deny in the PolicyLayer policy for create_task. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides create_task? +

create_task is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 678 Yaver tools → High-risk tools on this server →

Across the catalogue

diagram_create on Templonix Lite MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →