nw_trigger_save · Ppdm MCP: Risk & Policy

WHAT IT DOES

What nw_trigger_save does on Ppdm

AI agents invoke nw_trigger_save to trigger actions in Ppdm. 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 nw_trigger_save needs a policy

This tool executes an external operation (triggering a backup job) with side effects that cannot be easily predicted or reversed without additional operations. While backups are typically considered safe operations, the ability to trigger backups on arbitrary clients and potentially impact storage, network bandwidth, and system resources makes this an Execute-category tool.

From the tool's definition Tool description states it will 'Trigger an on-demand backup for a NetWorker client' - this initiates a backup operation whose effects depend on what data is backed up and the client configuration provided as arguments.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

nw_trigger_save Rate-limited

nw_trigger_save 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": {
    "nw_trigger_save": {
      "limits": [
        {
          "counter": "nw_trigger_save_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 Ppdm, so you can run agents against it safely.

FAQ

Questions about nw_trigger_save

What does the nw_trigger_save tool do? +

Trigger an on-demand backup for a NetWorker client. It is categorised as a Execute tool in the Ppdm MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on nw_trigger_save? +

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

What risk level is nw_trigger_save? +

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

Can I rate-limit nw_trigger_save? +

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

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

nw_trigger_save is provided by the Ppdm MCP server (moodswing9/ppdm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.