dephq_app_publish
Publish an owned app privately, or publish it privately and submit its Store listing for review.
This record as markdown: /tools/dephq-mcp/dephq-app-publish.md
What dephq_app_publish does on Dephq
AI agents use dephq_app_publish 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 | Yes | |
submit_for_listing | boolean | — |
Parameters from the server's own tool schema.
Why dephq_app_publish is rated Medium
Publishing an app and submitting it for Store review is a significant write operation that creates/modifies a public-facing artifact. It is not destructive (it doesn't delete) and not financial (no money moves), but misuse could expose unintended app versions to users or trigger a store review process that is difficult to retract, warranting high severity.
From the tool's definition Publish an owned app privately, or publish it privately and submit its Store listing for review
Attacks that exploit this kind of access
The rule that runs dephq_app_publish 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_publish, this is the rule to start with:
dephq_app_publish 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_app_publish call is checked against it from then on.
Questions about dephq_app_publish
Publish an owned app privately, or publish it privately and submit its Store listing for review. 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_app_publish accepts 2 parameters: app_id, submit_for_listing. 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_publish: 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_publish 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_app_publish 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_publish. 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_publish 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