dephq_app_unpublish
Return an owned Dephq app to draft and remove it from public use.
This record as markdown: /tools/dephq-mcp/dephq-app-unpublish.md
What dephq_app_unpublish does on Dephq
AI agents call dephq_app_unpublish to permanently remove resources in Dephq, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes |
Parameters from the server's own tool schema.
Why dephq_app_unpublish is rated Critical
Unpublishing an app removes it from public availability, which is an irreversible operational action in the sense that any users depending on the app lose access immediately. While technically the app could be re-published, the act of removing a live service from public use has high blast radius and is categorized as Destructive due to its irreversible impact on availability.
From the tool's definition 'remove it from public use' and 'Return an owned Dephq app to draft' — this action takes a live application offline, making it unavailable to users, which is not easily reversible in terms of service disruption.
Attacks that exploit this kind of access
The rule that runs dephq_app_unpublish 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_app_unpublish, this is the rule to start with:
dephq_app_unpublish is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Dephq, apply this rule, and every dephq_app_unpublish call is checked against it from then on.
Questions about dephq_app_unpublish
Return an owned Dephq app to draft and remove it from public use. It is categorised as a Destructive tool in the Dephq MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
dephq_app_unpublish accepts 1 parameter: app_id. Required: app_id. 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_app_unpublish: 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_app_unpublish is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the dephq_app_unpublish 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_app_unpublish. 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_app_unpublish 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.
Across the catalogue