verified_create_project · Tick MCP: Risk & Policy

WHAT IT DOES

What verified_create_project does on Tick

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

The tool creates a new project and optionally assigns it to a folder, which are reversible write operations. It does not execute arbitrary code, delete data irreversibly, move money, or merely read data. The verification step is confirmatory and does not elevate severity. Severity is medium because uncontrolled project creation could clutter workspaces and consume quota, but the impact is bounded and reversible.

From the tool's definition Tool description explicitly states it "Create[s] a project" and "verify[s]... that folder assignment persisted". These are reversible data creation operations characteristic of Write category.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

verified_create_project Rate-limited

verified_create_project 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_create_project": {
      "limits": [
        {
          "counter": "verified_create_project_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_create_project

What does the verified_create_project tool do? +

Create a project, then verify that it exists and that folder assignment persisted if requested. 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_create_project? +

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

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

Can I rate-limit verified_create_project? +

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

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

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