create_task

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 91 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 use create_task to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

Parameter	Type	Required	Description
`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-7, gpt-5-codex, or any opencode-configured provider/model). Empty = runner default.
`prompt`	string	Yes	The task prompt describing what the AI should do
`runner`	string	—	Runner ID — claude / codex / opencode. Empty = agent default.
`device_id`	string	—	Optional owned Yaver device id/name/alias to create the task on. Empty runs on the local MCP host.
`verbosity`	integer	—	Response detail level 0-10. 0=minimal ('done, no issues'), 5=moderate (key changes + reasoning), 10=full (all diffs, reasoning, alternatives). Default: 10.
`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 Medium

An AI agent can call create_task faster than any human can review: one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.

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 capped: an agent stuck in a loop can't make hundreds of changes 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": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does create_task accept? +

create_task accepts 9 parameters: mode, model, prompt, runner, device_id, verbosity, 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 Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

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 645 Yaver tools →

Across the catalogue

create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server →create_project on Stitch MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →