project_self_host_create

SERVERYaver SOURCEyaver-cli

Medium RISK CLASS

Category Write

Parameters 123 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/project-self-host-create.md

WHAT IT DOES

What project_self_host_create does on Yaver

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

RISK

Why project_self_host_create is rated Medium

This tool creates new project files and structure (monorepo, Next.js app, Expo app, packages, legal scaffolds) which constitutes reversible data creation/modification. It does not execute arbitrary code, delete data, move money, or trigger external operations beyond file generation.

From the tool's definition Tool description explicitly states it "create[s] the default self-hosted monorepo" and is "an alias of project_new_quick with the intended product defaults." Keywords: 'create' and specific mention of creating scaffolds, packages, and project structure.

Risk signalsHigh parameter count (21 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs project_self_host_create safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_self_host_create, this is the rule to start with:

project_self_host_create Rate-limited

project_self_host_create 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": {
    "project_self_host_create": {
      "limits": [
        {
          "counter": "project_self_host_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every project_self_host_create call is checked against it from then on.

FAQ

Questions about project_self_host_create

What does the project_self_host_create tool do? +

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.

What parameters does project_self_host_create accept? +

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.

How do I enforce a policy on project_self_host_create? +

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.

What risk level is project_self_host_create? +

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

Can I rate-limit project_self_host_create? +

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.

How do I block project_self_host_create completely? +

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.

What MCP server provides project_self_host_create? +

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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

create_project on Stitch MCP Server →create_task on 0rca Dojo MCP Server →create-task on Kanban MCP Server →create_package_backup on Android Forensics ADB MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →