run_database_backup · Ploi MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_database_backup does on Ploi MCP Server

AI agents invoke run_database_backup to trigger actions in Ploi MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_database_backup needs a policy

This tool executes a database backup operation, which is an action that triggers external infrastructure effects. While backups are generally reversible and not destructive themselves, running them has operational side effects (resource consumption, potential impact on database performance, backup storage).

From the tool's definition Tool name 'run_database_backup' combined with description 'Run an existing database backup configuration now' indicates execution of a predefined operation that triggers external database operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_database_backup Rate-limited

run_database_backup stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_database_backup": {
      "limits": [
        {
          "counter": "run_database_backup_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 run_database_backup

What does the run_database_backup tool do? +

Run an existing database backup configuration now (. It is categorised as a Execute tool in the Ploi MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_database_backup? +

Register the Ploi MCP Server MCP server in PolicyLayer and add a rule for run_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 run_database_backup? +

run_database_backup is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_database_backup? +

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

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

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