dephq_project_sync
Delta-sync a local Dephq app project to its creator-owned remote draft and wait for validation/build completion.
This record as markdown: /tools/dephq-mcp/dephq-project-sync.md
What dephq_project_sync does on Dephq
AI agents use dephq_project_sync 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 |
|---|---|---|---|
app_id | string | — | |
changelog | string | — | |
project_path | string | Yes | |
publish_privately | boolean | — |
Parameters from the server's own tool schema.
Why dephq_project_sync is rated Medium
The tool uploads/syncs local project files to a remote draft, which is a reversible write operation (draft state, not published). It modifies remote state but does not irreversibly delete or publish, though the blast radius is high since pushing incorrect code to a remote draft could corrupt or overwrite work and trigger a build pipeline.
From the tool's definition Delta-sync a local Dephq app project to its creator-owned remote draft
Attacks that exploit this kind of access
The rule that runs dephq_project_sync 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_sync, this is the rule to start with:
dephq_project_sync 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_sync call is checked against it from then on.
Questions about dephq_project_sync
Delta-sync a local Dephq app project to its creator-owned remote draft and wait for validation/build completion. 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_sync accepts 4 parameters: app_id, changelog, project_path, publish_privately. Required: 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_sync: 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_sync 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_sync 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_sync. 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_sync 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