project_new_quick
One-shot fullstack project scaffold. Skips the interactive wizard and creates a self-hosted-first monorepo (apps/{web,landing,mobile}, packages/shared, backend/) at parentDir/<slug>. Defaults are built for first-capture with Claude Code/Codex over MCP: local/dev Convex backend that can deploy to ...
This record as markdown: /tools/io-github-kivanccakmak-yaver/project-new-quick.md
What project_new_quick does on Yaver
AI agents invoke project_new_quick to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Brand name (shown in README, landing page, metadata) |
slug | string | Yes | URL-safe slug used for folder + package names |
domain | string | — | |
gitOrg | string | — | |
backend | string | — | |
problem | string | — | One-sentence user problem; defaults to description |
tagline | string | — | |
webHost | string | — | |
parentDir | string | — | Default: agent working dir |
includeWeb | boolean | — | Default true |
oauthApple | boolean | — | |
accentColor | string | — |
Parameters from the server's own tool schema.
Why project_new_quick is rated High
This tool executes a series of external operations: scaffolding a project on the filesystem, initializing git, and pushing to remote repositories. It triggers builds and external deployments. While it also writes files (Write), the execution of git operations, potential remote pushes, and triggering of build/deploy pipelines make Execute the most accurate category.
From the tool's definition One-shot fullstack project scaffold... Auto-inits git and pushes to GitHub/GitLab when gitProvider is set. Creates monorepo at parentDir/<slug>, native builds (xcodebuild + gradle), local/dev Convex backend that can deploy to hosted Convex
Risk signalsHigh parameter count (30 properties)
Attacks that exploit this kind of access
The rule that runs project_new_quick 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_new_quick, this is the rule to start with:
project_new_quick stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every project_new_quick call is checked against it from then on.
Questions about project_new_quick
One-shot fullstack project scaffold. Skips the interactive wizard and creates a self-hosted-first monorepo (apps/{web,landing,mobile}, packages/shared, backend/) at parentDir/<slug>. Defaults are built for first-capture with Claude Code/Codex over MCP: local/dev Convex backend that can deploy to hosted Convex, Next.js web on Cloudflare, static landing on Cloudflare Pages, Expo React Native mobile for iOS + Android, Apple/Google/email auth, native builds (xcodebuild + gradle, no EAS). Auto-inits git and pushes to GitHub/GitLab when gitProvider is set. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
project_new_quick accepts 12 parameters: name, slug, domain, gitOrg, backend, problem, tagline, webHost, parentDir, includeWeb, oauthApple, accentColor. Required: name, slug. 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_new_quick: 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_new_quick is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the project_new_quick 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_new_quick. 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_new_quick 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.
More on Yaver, and thousands of servers like it.
Across the catalogue