Full project bootstrap with deep project analysis. Reads package.json, Cargo.toml, go.mod, pom.xml, and other project manifests to generate perfectly tailored CLAUDE.md, .claude/ directory, settings.json with smart permissions, agents, .mcp.json, and .claudeignore. The generated CLAUDE.md includ...
Part of the Ccboot MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke ccboot_init_project to trigger processes or run actions in Ccboot. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
ccboot_init_project can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
ccboot_init_project:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Ccboot policy for all 16 tools.
Agents calling execute-class tools like ccboot_init_project have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
ccboot_init_project is one of the high-risk operations in Ccboot. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Full project bootstrap with deep project analysis. Reads package.json, Cargo.toml, go.mod, pom.xml, and other project manifests to generate perfectly tailored CLAUDE.md, .claude/ directory, settings.json with smart permissions, agents, .mcp.json, and .claudeignore. The generated CLAUDE.md includes real build commands, actual dependencies, framework-specific architecture rules, and detected patterns — not generic templates. Examples: ccboot_init_project({ project_path: '.', tech_stack: ['nextjs'], team_size: 5 }) ccboot_init_project({ project_path: './api', tech_stack: ['fastapi'], team_size: 12, compliance: ['hipaa'] }) ccboot_init_project({ project_path: '.', tech_stack: ['springboot'], team_size: 50, compliance: ['sox', 'soc2'] }) Returns: List of all generated files with descriptions. Error handling: Returns actionable suggestions if project_path doesn't exist or isn't writable.. It is categorised as a Execute tool in the Ccboot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Add a rule in your Intercept YAML policy under the tools section for ccboot_init_project. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Ccboot MCP server.
ccboot_init_project 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 ccboot_init_project rule in your Intercept 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 Intercept policy for ccboot_init_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.
ccboot_init_project is provided by the Ccboot MCP server (ccboot-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept