list_tasks

List all your Kling AI generation tasks with filtering options. View task history, check statuses, and filter by date range or status. Supports pagination for browsing through large task lists.

SERVERMCP Kling SOURCE199-mcp/mcp-kling

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/199-mcp-mcp-kling/list-tasks.md

WHAT IT DOES

What list_tasks does on MCP Kling

AI agents call list_tasks to retrieve information from MCP Kling 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 existing data (task history and statuses) without modifying, deleting, executing code, or incurring financial obligations. It is a pure read operation that provides visibility into past generation tasks.

From the tool's definition Tool description states it "List[s] all your Kling AI generation tasks" and allows users to "View task history, check statuses, and filter by date range or status" with "pagination for browsing." These are query/retrieval operations with no side effects.

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 MCP Kling, 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 MCP Kling, 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 your Kling AI generation tasks with filtering options. View task history, check statuses, and filter by date range or status. Supports pagination for browsing through large task lists. It is categorised as a Read tool in the MCP Kling MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_tasks? +

Register the MCP Kling 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 MCP Kling. 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 MCP Kling MCP server (199-mcp/mcp-kling). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on MCP Kling, and thousands of servers like it.

This server

All 12 MCP Kling 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 →