pause_time_machine · NDB MCP Server MCP: Risk & Policy

WHAT IT DOES

What pause_time_machine does on NDB MCP Server

AI agents invoke pause_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 pause_time_machine needs a policy

Pausing a time machine is a reversible operational action (it can be resumed), but it triggers an external operation that halts backup/snapshot activity on NDB. This is not a simple data read or write — it actively changes the operational state of the time machine, preventing new snapshots and log catchups from running. This could expose databases to data loss risk during the paused period, making it high severity.

From the tool's definition 'Pause a time machine. When paused, no new snapshots nor log catchup will be taken until it is resumed.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pause_time_machine Rate-limited

pause_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": {
    "pause_time_machine": {
      "limits": [
        {
          "counter": "pause_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 pause_time_machine

What does the pause_time_machine tool do? +

Pause a time machine. When paused, no new snapshots nor log catchup will be taken until it is resumed. 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 pause_time_machine? +

Register the NDB MCP Server MCP server in PolicyLayer and add a rule for pause_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 pause_time_machine? +

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

Can I rate-limit pause_time_machine? +

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

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

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