update_database_backup · Coolify MCP Tools MCP

WHAT IT DOES

What update_database_backup does on Coolify MCP Tools

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

WHY IT NEEDS A POLICY

Why update_database_backup needs a policy

The tool modifies backup configuration (a write operation) rather than executing backups, deleting data, or moving money. However, misconfiguration of backups could have severe operational consequences—incorrect scheduling or retention settings could lead to data loss if an AI agent disables backups or sets invalid parameters.

From the tool's definition Tool name 'update_database_backup' and description 'Update a scheduled backup configuration' indicate modification of existing backup settings. This is a reversible write operation affecting infrastructure configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_database_backup Rate-limited

update_database_backup 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": {
    "update_database_backup": {
      "limits": [
        {
          "counter": "update_database_backup_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 Coolify MCP Tools, so you can run agents against it safely.

FAQ

Questions about update_database_backup

What does the update_database_backup tool do? +

Update a scheduled backup configuration. It is categorised as a Write tool in the Coolify MCP Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_database_backup? +

Register the Coolify MCP Tools MCP server in PolicyLayer and add a rule for update_database_backup: 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 Coolify MCP Tools. Nothing to install.

What risk level is update_database_backup? +

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

Can I rate-limit update_database_backup? +

Yes. Add a rate_limit block to the update_database_backup 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 update_database_backup completely? +

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

update_database_backup is provided by the Coolify MCP Tools MCP server (jplansink/coolify-mcp-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.