verified_batch_move · Tick MCP: Risk & Policy

WHAT IT DOES

What verified_batch_move does on Tick

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

This tool modifies task state by moving/repositioning multiple tasks (batch operation) but does not destroy data—tasks remain intact after relocation. The explicit mention of 'rollback hints' and 'verification' reinforces that the operation is reversible.

From the tool's definition Tool name 'batch_move' indicates bulk relocation of tasks; description mentions 'verified' wrapper with 'rollback hints', confirming reversibility and non-destructive modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verified_batch_move Rate-limited

verified_batch_move 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_batch_move": {
      "limits": [
        {
          "counter": "verified_batch_move_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_batch_move

What does the verified_batch_move tool do? +

Verified batch move wrapper with rollback hints if verification fails. 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_batch_move? +

Register the Tick MCP server in PolicyLayer and add a rule for verified_batch_move: 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_batch_move? +

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

Can I rate-limit verified_batch_move? +

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

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

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