rollback
Roll a DenkOps project back to a previous healthy version (omit version for the previous one).
This record as markdown: /tools/denkopsai-mcp/rollback.md
What rollback does on Denkopsai
AI agents call rollback to retrieve information from Denkopsai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
version | integer | — | |
project_id | string | Yes |
Parameters from the server's own tool schema.
Why rollback is rated Low
Even though rollback only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs rollback safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Denkopsai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rollback, this is the rule to start with:
rollback is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Denkopsai, apply this rule, and every rollback call is checked against it from then on.
Questions about rollback
Roll a DenkOps project back to a previous healthy version (omit version for the previous one). It is categorised as a Read tool in the Denkopsai MCP Server, which means it retrieves data without modifying state.
rollback accepts 2 parameters: version, project_id. Required: project_id. The full parameter table on this page comes from the server's own tool schema.
Register the Denkopsai MCP server in PolicyLayer and add a rule for 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 Denkopsai. Nothing to install.
rollback is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the 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 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.
rollback is provided by the Denkopsai MCP server (@denkopsai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Denkopsai, and thousands of servers like it.
This server
Across the catalogue