dephq_app_rollback
Restore an owned app's source from a selected historical version. This creates a new current version.
This record as markdown: /tools/dephq-mcp/dephq-app-rollback.md
What dephq_app_rollback does on Dephq
AI agents use dephq_app_rollback 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 | |
version_id | string | Yes |
Parameters from the server's own tool schema.
Why dephq_app_rollback is rated Medium
The rollback operation replaces the current app source with a historical version and creates a new current version. This is a Write/modify operation (not Destructive since the historical versions remain intact and a new version is created rather than deleting data).
From the tool's definition Restore an owned app's source from a selected historical version. This creates a new current version.
Attacks that exploit this kind of access
The rule that runs dephq_app_rollback 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_rollback, this is the rule to start with:
dephq_app_rollback 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_rollback call is checked against it from then on.
Questions about dephq_app_rollback
Restore an owned app's source from a selected historical version. This creates a new current version. 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_rollback accepts 2 parameters: app_id, version_id. Required: app_id, version_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_rollback: 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_rollback 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_rollback 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_rollback. 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_rollback 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