// SCAN REPORT

Neptune MCP Server

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

1 destructive tool with no built-in limits. Policy required.

Last updated: 11 Jun 2026

8 can modify or destroy data

7 read-only

15 tools total

Community server · catalogue entry verified 11/06/2026

How to control Neptune MCP Server ↓

TOOL MAP

What Neptune MCP Server exposes to your agents

Read (7) Write / Execute (6) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Neptune MCP Server tools

Destructive · High delete_project The name 'delete_project' indicates an irreversible deletion operation that cannot be undone. Execute · High deploy_project This tool executes deployment operations to AWS infrastructure, which is a significant external operation whose effects depend on what project is being deployed and the infrastructure inferred. Execute · High wait_for_deployment This tool likely waits for an ongoing deployment to complete, which is an external operation with side effects. Execute · High provision_resources The tool name 'provision_resources' strongly implies creating/spinning up cloud infrastructure resources on AWS.

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

POLICY

How to control Neptune MCP Server

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

Deny destructive operations

{
  "delete_project": {
    "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

{
  "add_new_resource": {
    "limits": [
      {
        "counter": "add_new_resource_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_bucket_object": {
    "limits": [
      {
        "counter": "get_bucket_object_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 Neptune 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 NEPTUNE →

Free to start. No card required.

FULL CATALOGUE

All 15 Neptune MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_project delete_project

EXECUTE 4 tools

Execute deploy_project deploy_project Execute wait_for_deployment wait_for_deployment Execute provision_resources provision_resources Execute query_database query_database

WRITE 2 tools

Write add_new_resource add_new_resource Write set_secret_value set_secret_value

READ 7 tools

Read get_bucket_object get_bucket_object Read get_deployment_status get_deployment_status Read get_logs get_logs Read get_project_schema get_project_schema Read info info Read list_bucket_files list_bucket_files Read list_projects list_projects

OTHER 1 tools

EXPLORE

Related servers

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

FAQ

Questions about Neptune MCP Server

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

Yes. The Neptune MCP Server server exposes 1 destructive tools including delete_project. 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 Neptune MCP Server? +

The Neptune MCP Server server has 2 write tools including add_new_resource, set_secret_value. 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 Neptune MCP Server.

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

15 tools across 4 categories: Destructive, Execute, Read, Write. 7 are read-only. 8 can modify, create, or delete data.

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

Register the Neptune 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 Neptune MCP Server tool call.

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

ENFORCE POLICY ON NEPTUNE →

Free to start. No card required.

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