list_tasks

List all tasks and their current status (queued, running, completed, failed, stopped). Each task may also expose remote demo video artifacts via videoClipId/videoStatus/videoClipUrl/videoPosterUrl.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/list-tasks.md

WHAT IT DOES

What list_tasks does on Yaver

AI agents call list_tasks to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_tasks is rated Low

This tool retrieves and queries task information without side effects. It exposes status metadata and artifact references but does not create, modify, delete, or execute any operations. The capability to view video artifact metadata does not constitute write or execute risk. Low severity due to limited blast radius—an agent listing tasks cannot harm system state or data integrity.

From the tool's definition Tool description explicitly states 'List all tasks and their current status' with read-only exposure of task metadata and artifact references (videoClipId, videoStatus, videoClipUrl, videoPosterUrl).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_tasks 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 list_tasks, this is the rule to start with:

list_tasks Allowed

list_tasks is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_tasks": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_tasks

What does the list_tasks tool do? +

List all tasks and their current status (queued, running, completed, failed, stopped). Each task may also expose remote demo video artifacts via videoClipId/videoStatus/videoClipUrl/videoPosterUrl. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tasks? +

Register the Yaver MCP server in PolicyLayer and add a rule for list_tasks: 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 list_tasks? +

list_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_tasks? +

Yes. Add a rate_limit block to the list_tasks 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 list_tasks completely? +

Set action: deny in the PolicyLayer policy for list_tasks. 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 list_tasks? +

list_tasks 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

list_tasks on 0rca Dojo MCP Server →aiva_list_affiliates on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →