verified_move_tasks · Tick MCP: Risk & Policy

WHAT IT DOES

What verified_move_tasks does on Tick

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

Moving tasks between projects is a write operation that changes task metadata (project_id or parent reference) but is reversible—tasks can be moved back. This falls under Write rather than Execute because it doesn't trigger external side effects or arbitrary code execution; it modifies a structured data model in a predictable way. The verification step does not escalate the category.

From the tool's definition Tool description states 'Move tasks' which modifies the project assignment of tasks, a reversible data modification operation. Verification step is a read-only confirmation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verified_move_tasks Rate-limited

verified_move_tasks 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": {
    "verified_move_tasks": {
      "limits": [
        {
          "counter": "verified_move_tasks_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 verified_move_tasks

What does the verified_move_tasks tool do? +

Move tasks, then verify that each moved task is present in the destination project. 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 verified_move_tasks? +

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

What risk level is verified_move_tasks? +

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

Can I rate-limit verified_move_tasks? +

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

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

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