create_database_backup · Ploi MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_database_backup does on Ploi MCP Server

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

WHY IT NEEDS A POLICY

Why create_database_backup needs a policy

This tool creates a backup configuration, which is a reversible modification of system state. It does not delete data (which would be Destructive), execute arbitrary code (Execute), or move money (Financial). The backup configuration itself can be updated or deleted later.

From the tool's definition Tool name 'create_database_backup' and description 'Create a SCHEDULED database backup configuration' indicate data modification—specifically creating a new backup schedule/configuration object.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_database_backup Rate-limited

create_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": {
    "create_database_backup": {
      "limits": [
        {
          "counter": "create_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 Ploi MCP Server, so you can run agents against it safely.

FAQ

Questions about create_database_backup

What does the create_database_backup tool do? +

Create a SCHEDULED database backup configuration. Requires a pre-existing backup destination (backup_configuration id — see Ploi. It is categorised as a Write tool in the Ploi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_database_backup? +

Register the Ploi MCP Server MCP server in PolicyLayer and add a rule for create_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 Ploi MCP Server. Nothing to install.

What risk level is create_database_backup? +

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

Can I rate-limit create_database_backup? +

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

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

create_database_backup is provided by the Ploi MCP Server MCP server (sudanese/ploi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

create_database_backup is one line of Ploi MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →