tasks

Inspect durable background tasks and flows

SERVEROpenClaw SOURCEopenclaw

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity verified Pull the record →

This record as markdown: /tools/openclaw/tasks.md

WHAT IT DOES

What tasks does on OpenClaw

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

RISK

Why tasks is rated Low

The tool is described as inspecting (viewing/querying) background tasks and flows. This is a read operation that retrieves state information without modifying or executing anything. Severity is low as misuse would only expose task metadata.

From the tool's definition 'Inspect durable background tasks and flows' — 'Inspect' indicates a read-only, observational operation with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs tasks safely

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

tasks Allowed

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": {
    "tasks": {}
  }
}

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

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

FAQ

Questions about tasks

What does the tasks tool do? +

Inspect durable background tasks and flows. It is categorised as a Read tool in the OpenClaw MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on tasks? +

Register the OpenClaw MCP server in PolicyLayer and add a rule for 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 OpenClaw. Nothing to install.

What risk level is tasks? +

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

Can I rate-limit tasks? +

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

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

tasks is provided by the OpenClaw MCP server (openclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on OpenClaw, and thousands of servers like it.

This server

All 129 OpenClaw tools →

Across the catalogue

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

Guides

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