verified_assign_project_folder · Tick MCP: Risk & Policy

WHAT IT DOES

What verified_assign_project_folder does on Tick

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

This tool creates or modifies data reversibly by reassigning a project's folder location. While it changes application state, the action is not irreversible (a project can be reassigned to a different folder), does not delete data, and does not execute arbitrary code or move financial resources. It fits the Write category.

From the tool's definition Tool name includes 'assign' and description states 'Assign a project to a folder' — this modifies the organizational structure of a project by changing its folder/groupId association. The verification through V2 sync confirms persistence of the change.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verified_assign_project_folder Rate-limited

verified_assign_project_folder 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_assign_project_folder": {
      "limits": [
        {
          "counter": "verified_assign_project_folder_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_assign_project_folder

What does the verified_assign_project_folder tool do? +

Assign a project to a folder and verify the persisted groupId through V2 sync. 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_assign_project_folder? +

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

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

Can I rate-limit verified_assign_project_folder? +

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

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

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