// SCAN REPORT

NDB MCP Server

43 tools. 15 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated: 4 Jul 2026

15 can modify or destroy data

28 read-only

43 tools total

Community server · catalogue entry verified 04/07/2026

How to control NDB MCP Server ↓

TOOL MAP

What NDB MCP Server exposes to your agents

Read (28) Write / Execute (11) Destructive / Financial (4)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous NDB MCP Server tools

Destructive · High delete_clone This tool permanently deletes data and resources without the ability to undo the operation. Destructive · Critical delete_dbserver This tool irreversibly deletes database infrastructure—the dbserver and potentially its associated VM. Destructive · High delete_snapshot Snapshots are critical backup artifacts used for disaster recovery and data protection. Destructive · Critical deregister_database This tool performs irreversible operations: deregistering a database from NDB management cannot be undone, and the delete=true variant permanently destroys the database.

15 of NDB MCP Server's 43 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control NDB MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and NDB MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_clone": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "create_clone": {
    "limits": [
      {
        "counter": "create_clone_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_alert": {
    "limits": [
      {
        "counter": "get_alert_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register NDB MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON NDB →

Instant setup, no code required.

FULL CATALOGUE

All 43 NDB MCP Server tools

DESTRUCTIVE 4 tools

Destructive delete_clone Delete a clone Key Features: - Removes the clone and its associated resources (delete = true) - C Destructive delete_dbserver Deregister (delete) a database server from NDB. This operation removes the dbserver and optionally its associa Destructive delete_snapshot Delete a snapshot Destructive deregister_database Deregister a database from NDB which means the database will no longer be managed by NDB. This does not delete

EXECUTE 3 tools

Execute create_dbserver Create a new database server VM on a Nutanix cluster, without the database with intelligent parameter validati Execute pause_time_machine Pause a time machine. When paused, no new snapshots nor log catchup will be taken until it is resumed. Execute resume_time_machine Resume a paused time machine. When resumed, snapshots and log catchup will continue as per the defined schedul

WRITE 8 tools

Write create_clone 🚨 START HERE FOR ALL DATABASE CLONING 🚨 Create a clone from a time machine using NDB with intelligent parame Write grant_time_machine_access Grant access to a time machine to another Nutanix cluster, using a specified SLA policy for that cluster. That Write register_database Register an existing database with NDB Write register_dbserver Register an existing database server with NDB Write restore_database Restore a database to a specific point in time or from a snapshot. This operation allows you to recover a data Write take_snapshot Take a snapshot of a time machine Write update_database Update database name, description, or tags Write update_time_machine Update a Time Machine

READ 28 tools

Read get_alert Get alert details by ID Read get_clone Get clone details by ID, name, or database name Read get_cluster Get cluster details by ID Read get_cluster_by_name Get cluster details by name Read get_current_user Get the current authenticated NDB user. Returns user details for the account associated with the current authe Read get_database Get detailed (not filtered) information for a specific database. Returns comprehensive database details includ Read get_dbserver Get database server details Read get_operation Get operation details by ID Read get_profile Get profile details by ID or name Read get_sla Get SLA details by ID or name Read get_snapshot Get snapshot details by ID Read get_time_machine Get time machine details Read get_time_machine_access List all Nutanix clusters that have access to a specific Time Machine, alongside their SLA policies. Read get_time_machine_capability Get recovery capability of a time machine Read get_user Get user details by user ID Read list_alerts Get list of all alerts with advanced filtering options. Returns a reduced set of fields for each alert. API-s Read list_clones Get all database clones. Filtering is done using valueType and value fields, which are used to filter the resp Read list_clusters Get list of all Nutanix clusters with advanced filtering and reduced schema mapping. Returns only the most rel Read list_databases Get all registered and provisioned database instances with comprehensive filtering options. Returns a list of Read list_dbservers Get all database servers. You can include information about databases and/or clones hosted on the db server by Read list_operations Get list of operations (short info) with all supported filters from the NDB API. Available parameters: - dbse Read list_profiles Get a list of all profiles with advanced filtering options. Profile types: - Software: The image that will be Read list_roles List roles tool: calls /roles endpoint and returns an array of role objects. Returned Information: - Read list_slas Get list of all SLAs Read list_snapshots Get list of all snapshots Read list_time_machines Get list of all time machines. Returns a summarized list of time machines with key fields only. Returned fiel Read list_users Get all NDB users. Filtering is done using valueType and value fields, which are used to filter the response s Read refresh_clone Refresh a clone with latest data. Key Features: - Supports refreshing from a specific snapshot or the

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about NDB MCP Server

Can an AI agent delete data through the NDB MCP Server MCP server? +

Yes. The NDB MCP Server server exposes 4 destructive tools including delete_clone, delete_dbserver, delete_snapshot. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through NDB MCP Server? +

The NDB MCP Server server has 8 write tools including create_clone, grant_time_machine_access, register_database. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach NDB MCP Server.

How many tools does the NDB MCP Server MCP server expose? +

43 tools across 3 categories: Destructive, Read, Write. 28 are read-only. 15 can modify, create, or delete data.

How do I enforce a policy on NDB MCP Server? +

Register the NDB MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every NDB MCP Server tool call.

Deterministic rules across all 43 NDB MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NDB →

Instant setup, no code required.

43 NDB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.