Create a new blank project. Defaults to the current account organization and waits for the project to appear in search. Creates a pre- or post-type-system-refactor project automatically based on the account rollout; pass useNewType/useRefactoredComponent to override.
AI agents use create_project to create or update resources in Zion — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zion environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
wait | boolean | — | |
category | string | null | — | |
platform | string | null | — | |
timeoutMs | number | — | |
useNewType | boolean | — | |
projectName | string | Yes | |
templateExId | string | null | — | |
forBeginnerGuide | boolean | — | |
organizationExId | string | — | |
projectSpaceType | string | — | |
useRefactoredComponent | boolean | — |
Parameters from the server's own tool schema.
Creating a project in an account is a Write operation: it results in persistent data modification but is reversible (projects can be deleted). The tool accepts organizational context and type-system parameters. While account-scoped, this is not as severe as Destructive (no permanent data loss) or Financial (no money movement).
From the tool's definition Tool description states "Create a new blank project" - a reversible creation operation that modifies account/organizational data. No mention of deletion, financial transaction, or code execution.
Risk signalsHigh parameter count (11 properties)
Attacks that exploit this kind of access
Create a new blank project. Defaults to the current account organization and waits for the project to appear in search. Creates a pre- or post-type-system-refactor project automatically based on the account rollout; pass useNewType/useRefactoredComponent to override. It is categorised as a Write tool in the Zion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_project accepts 11 parameters: wait, category, platform, timeoutMs, useNewType, projectName, templateExId, forBeginnerGuide, organizationExId, projectSpaceType, useRefactoredComponent. Required: projectName. The full parameter table on this page comes from the server's own tool schema.
Register the Zion 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 Zion. 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 Zion MCP server (zion-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 →