resume_time_machine · NDB MCP Server MCP: Risk & Policy

WHAT IT DOES

What resume_time_machine does on NDB MCP Server

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

This tool triggers an external operation — resuming a paused time machine service in NDB — which causes ongoing automated processes (snapshots, log catchup) to restart. It does not merely read data, nor does it irreversibly destroy data, but it does initiate and alter the behavior of a running service, making Execute the most appropriate category.

From the tool's definition Resume a paused time machine. When resumed, snapshots and log catchup will continue as per the defined schedule and SLA.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

resume_time_machine Rate-limited

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

FAQ

Questions about resume_time_machine

What does the resume_time_machine tool do? +

Resume a paused time machine. When resumed, snapshots and log catchup will continue as per the defined schedule and SLA. It is categorised as a Execute tool in the NDB 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 resume_time_machine? +

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

What risk level is resume_time_machine? +

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

Can I rate-limit resume_time_machine? +

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

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

resume_time_machine is provided by the NDB MCP Server MCP server (rouxton/ndb-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.