set_task_hierarchy · Agentic Task System MCP: Risk & Policy

WHAT IT DOES

What set_task_hierarchy does on Agentic Task System

AI agents use set_task_hierarchy 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_hierarchy needs a policy

This tool modifies task hierarchy metadata by changing role assignments and parent relationships. These are reversible operations (the parent relationship can be reassigned or cleared), placing it squarely in the Write category rather than Destructive. The severity is medium because misuse could corrupt task organization and relationships, but the changes are recoverable.

From the tool's definition Tool description explicitly states "WRITE" and describes assigning roles and modifying parent relationships, which are reversible data modifications. The verb "assigns" and "replaces" indicate creation/modification operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_task_hierarchy Rate-limited

set_task_hierarchy 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_hierarchy": {
      "limits": [
        {
          "counter": "set_task_hierarchy_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_hierarchy

What does the set_task_hierarchy tool do? +

WRITE. Assigns an exploration/goal/project/task role and optionally replaces or clears the single explicit parent relationship. 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_hierarchy? +

Register the Agentic Task System MCP server in PolicyLayer and add a rule for set_task_hierarchy: 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_hierarchy? +

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

Can I rate-limit set_task_hierarchy? +

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

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

set_task_hierarchy 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.