generate_rollback · Safe Migrations MCP: Risk & Policy

WHAT IT DOES

What generate_rollback does on Safe Migrations

AI agents use generate_rollback to create or update resources in Safe Migrations — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Safe Migrations environment.

WHY IT NEEDS A POLICY

Why generate_rollback needs a policy

generate_rollback produces SQL undo statements and restoration plans, which are reversible data modifications (Write category). It does not execute these changes, so it is not Execute or Destructive. The severity is medium because while the generated SQL could be dangerous if misapplied, the tool itself only produces instructions within a gated migration system.

From the tool's definition Tool description: 'Produce exact undo SQL (for DB proposals) or a restore plan (for config).' The tool generates reversible restoration instructions rather than executing destructive changes. It creates SQL and plans but does not apply them.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_rollback Rate-limited

generate_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "generate_rollback": {
      "limits": [
        {
          "counter": "generate_rollback_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Safe Migrations, so you can run agents against it safely.

FAQ

Questions about generate_rollback

What does the generate_rollback tool do? +

Produce exact undo SQL (for DB proposals) or a restore plan (for config). It is categorised as a Write tool in the Safe Migrations MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_rollback? +

Register the Safe Migrations MCP server in PolicyLayer and add a rule for generate_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 Safe Migrations. Nothing to install.

What risk level is generate_rollback? +

generate_rollback is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit generate_rollback? +

Yes. Add a rate_limit block to the generate_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.

How do I block generate_rollback completely? +

Set action: deny in the PolicyLayer policy for generate_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.

What MCP server provides generate_rollback? +

generate_rollback is provided by the Safe Migrations MCP server (possibly6/safe-migrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.