grant_time_machine_access · NDB MCP Server MCP

WHAT IT DOES

What grant_time_machine_access does on NDB MCP Server

AI agents use grant_time_machine_access to create or update resources in NDB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your NDB MCP Server environment.

WHY IT NEEDS A POLICY

Why grant_time_machine_access needs a policy

This tool modifies access control by granting another cluster access to a time machine resource, and applies an SLA policy to it. This is a reversible write/configuration change (access can presumably be revoked), but it has high blast radius because it exposes sensitive database backup/snapshot data (time machine) to an external cluster, potentially enabling unauthorized data access if misused.

From the tool's definition Grant access to a time machine to another Nutanix cluster, using a specified SLA policy for that cluster

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

grant_time_machine_access Rate-limited

grant_time_machine_access stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "grant_time_machine_access": {
      "limits": [
        {
          "counter": "grant_time_machine_access_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 grant_time_machine_access

What does the grant_time_machine_access tool do? +

Grant access to a time machine to another Nutanix cluster, using a specified SLA policy for that cluster. That SLA can. It is categorised as a Write tool in the NDB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on grant_time_machine_access? +

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

grant_time_machine_access is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit grant_time_machine_access? +

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

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

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