First-capture MCP tool for a new Yaver user: create the default self-hosted monorepo without asking them to touch npm/yaver CLI. This is an alias of project_new_quick with the intended product defaults: Convex local/dev backend (cloud-deployable later), Next.js Cloudflare web UI, Cloudflare landi...
AI agents use project_self_host_create to create or update resources in Yaver — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
slug | string | Yes | |
domain | string | — | |
gitOrg | string | — | |
problem | string | — | |
tagline | string | — | |
parentDir | string | — | |
accentColor | string | — | |
appTemplate | string | — | |
description | string | Yes | |
gitProvider | string | — | |
iosBundleId | string | — |
Parameters from the server's own tool schema.
An AI agent can call project_self_host_create faster than any human can review — one bad instruction and it creates or modifies resources in Yaver by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (21 properties)
Attacks that exploit this kind of access
First-capture MCP tool for a new Yaver user: create the default self-hosted monorepo without asking them to touch npm/yaver CLI. This is an alias of project_new_quick with the intended product defaults: Convex local/dev backend (cloud-deployable later), Next.js Cloudflare web UI, Cloudflare landing page, Expo React Native iOS/Android app, shared package, legal/store-review scaffolds, and next steps for Yaver phone testing. Use this before suggesting hourly Yaver Managed Cloud. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
project_self_host_create accepts 12 parameters: name, slug, domain, gitOrg, problem, tagline, parentDir, accentColor, appTemplate, description, gitProvider, iosBundleId. Required: name, slug, description. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for project_self_host_create: 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 Yaver. Nothing to install.
project_self_host_create 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 project_self_host_create 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 project_self_host_create. 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.
project_self_host_create is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.