AI agents use create_project to create or update resources in Tickr — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tickr environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Project display name |
slug | string | Yes | URL-safe project slug (unique) |
prefix | string | Yes | Ticket prefix, e.g. 'VLX', 'TKR' |
description | string | — | Project description |
Parameters from the server's own tool schema.
This tool creates a new project entity in the project management system. Creation of projects is a Write operation because it adds new data to the system but remains reversible (projects can typically be deleted or archived). While it affects system state, it does not trigger external code execution, permanently destroy data, or involve financial transactions.
From the tool's definition Tool name 'create_project' and description 'Create a new project' indicate data creation capability that modifies project management state reversibly.
Attacks that exploit this kind of access
Create a new project. It is categorised as a Write tool in the Tickr MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_project accepts 4 parameters: name, slug, prefix, description. Required: name, slug, prefix. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr MCP server in PolicyLayer and add a rule for 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 Tickr. Nothing to install.
create_project is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
create_project is provided by the Tickr MCP server (@k-system/tickr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →