dephq_project_init
Scaffold a complete Dephq React and TypeScript project. Choose a page, records app, API-backed tool, or full app with frontend and server capabilities. Creation is transactional and existing files are never overwritten.
This record as markdown: /tools/dephq-mcp/dephq-project-init.md
What dephq_project_init does on Dephq
AI agents use dephq_project_init to create or update resources in Dephq, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dephq environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | |
slug | string | — | |
access | string | — | |
framework | string | — | |
description | string | — | |
capabilities | array | — | |
project_path | string | Yes | |
project_type | string | — | |
install_dependencies | boolean | — |
Parameters from the server's own tool schema.
Why dephq_project_init is rated Medium
This tool creates new project files and scaffolding. It explicitly states existing files are never overwritten, making it a reversible write operation (new file creation) rather than destructive. The severity is medium since it creates potentially many files on the filesystem, but misuse has limited blast radius given the no-overwrite guarantee.
From the tool's definition Scaffold a complete Dephq React and TypeScript project... Creation is transactional and existing files are never overwritten.
Attacks that exploit this kind of access
The rule that runs dephq_project_init safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Dephq, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For dephq_project_init, this is the rule to start with:
dephq_project_init 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Dephq, apply this rule, and every dephq_project_init call is checked against it from then on.
Questions about dephq_project_init
Scaffold a complete Dephq React and TypeScript project. Choose a page, records app, API-backed tool, or full app with frontend and server capabilities. Creation is transactional and existing files are never overwritten. It is categorised as a Write tool in the Dephq MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
dephq_project_init accepts 9 parameters: name, slug, access, framework, description, capabilities, project_path, project_type, install_dependencies. Required: name, project_path. The full parameter table on this page comes from the server's own tool schema.
Register the Dephq MCP server in PolicyLayer and add a rule for dephq_project_init: 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 Dephq. Nothing to install.
dephq_project_init 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 dephq_project_init 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 dephq_project_init. 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.
dephq_project_init is provided by the Dephq MCP server (@dephq/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Dephq, and thousands of servers like it.
This server
Across the catalogue