set_task_lifecycle · Agentic Task System MCP: Risk & Policy

WHAT IT DOES

What set_task_lifecycle does on Agentic Task System

AI agents use set_task_lifecycle to create or update resources in Agentic Task System — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agentic Task System environment.

WHY IT NEEDS A POLICY

Why set_task_lifecycle needs a policy

This tool modifies task metadata (lifecycle state and validity windows) but does not delete data or execute arbitrary operations. It is reversible—states can be changed back. The blast radius is medium because incorrect lifecycle changes could hide tasks from view or affect task visibility in the system, but data remains intact and recoverable.

From the tool's definition Tool description states it "Sets portable lifecycle state and validity windows". The explicit "WRITE" prefix and the verb "Sets" indicate data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_task_lifecycle Rate-limited

set_task_lifecycle 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": {
    "set_task_lifecycle": {
      "limits": [
        {
          "counter": "set_task_lifecycle_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Agentic Task System, so you can run agents against it safely.

FAQ

Questions about set_task_lifecycle

What does the set_task_lifecycle tool do? +

WRITE. Sets portable lifecycle state and validity windows. Archived, expired, future, and superseded tasks are excluded by context assembly. It is categorised as a Write tool in the Agentic Task System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on set_task_lifecycle? +

Register the Agentic Task System MCP server in PolicyLayer and add a rule for set_task_lifecycle: 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 Agentic Task System. Nothing to install.

What risk level is set_task_lifecycle? +

set_task_lifecycle is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit set_task_lifecycle? +

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

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

set_task_lifecycle is provided by the Agentic Task System MCP server (renezander030/agentic-task-system). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.