create_subtask · Tick MCP: Risk & Policy

WHAT IT DOES

What create_subtask does on Tick

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

WHY IT NEEDS A POLICY

Why create_subtask needs a policy

This tool creates a new subtask entity, which is a write operation that modifies the task hierarchy. It is reversible (subtasks can be deleted) and has a medium blast radius if an AI agent creates excessive or malformed subtasks, potentially cluttering a user's task management system. It does not execute external code, destroy data irreversibly, or move money.

From the tool's definition Tool name 'create_subtask' and description 'Create a child task' indicate data creation. The phrase 'verify the parent-child relationship afterwards' confirms a reversible write operation with no deletion or financial impact.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_subtask Rate-limited

create_subtask 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": {
    "create_subtask": {
      "limits": [
        {
          "counter": "create_subtask_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 Tick, so you can run agents against it safely.

FAQ

Questions about create_subtask

What does the create_subtask tool do? +

Create a child task and verify the parent-child relationship afterwards. It is categorised as a Write tool in the Tick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_subtask? +

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

What risk level is create_subtask? +

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

Can I rate-limit create_subtask? +

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

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

create_subtask is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.