plesk_backup_trigger · Plesk MCP Server MCP: Risk & Policy

WHAT IT DOES

What plesk_backup_trigger does on Plesk MCP Server

AI agents invoke plesk_backup_trigger to trigger actions in Plesk 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 plesk_backup_trigger needs a policy

This tool executes a backup operation, which is an external process with side effects that cannot be reversed by simply re-running the tool. While backups are generally beneficial, misuse by an AI agent (e.g., triggering excessive backups, targeting wrong domains, resource exhaustion) creates operational risk.

From the tool's definition Tool name 'plesk_backup_trigger' and description 'Trigger a manual backup for a specific domain' indicate the tool initiates an external operation (backup process) whose effects depend on the domain argument provided.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

plesk_backup_trigger Rate-limited

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

FAQ

Questions about plesk_backup_trigger

What does the plesk_backup_trigger tool do? +

Trigger a manual backup for a specific domain. It is categorised as a Execute tool in the Plesk 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 plesk_backup_trigger? +

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

What risk level is plesk_backup_trigger? +

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

Can I rate-limit plesk_backup_trigger? +

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

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

plesk_backup_trigger is provided by the Plesk MCP Server MCP server (klan1/plesk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.