manage_columns · Tick MCP: Risk & Policy

WHAT IT DOES

What manage_columns does on Tick

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

Without a description, confidence is reduced. The name 'manage_columns' implies creating, reordering, or modifying column definitions in a task management system—a reversible Write operation. It is not Read (read-only), not Destructive (columns can typically be modified or recreated), not Execute (no code/command execution implied), and not Financial.

From the tool's definition Tool name 'manage_columns' suggests modification of task/project structure. No description provided. Sibling tools include create_project, batch_update_tasks, and create_subtask, indicating this server performs Write operations on TickTick data structures.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

manage_columns Rate-limited

manage_columns 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": {
    "manage_columns": {
      "limits": [
        {
          "counter": "manage_columns_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 manage_columns

What does the manage_columns tool do? +

manage_columns. 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 manage_columns? +

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

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

Can I rate-limit manage_columns? +

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

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

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