4 tools. 2 can modify or destroy data without limits.
2 write tools that can modify data. Rate limits recommended.
Last updated:
Execute tools (run_gremlin_query, run_opencypher_query) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
get_graph_schema:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
The AWS Labs Amazon Neptune MCP Server server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.
4 tools across 2 categories: Execute, Read. 2 are read-only. 2 can modify, create, or delete data.
One line change. Instead of running the AWS Labs Amazon Neptune MCP Server server directly, prefix it with Intercept: intercept -c aws-labs-amazon-neptune-mcp-server.yaml -- npx -y @awslabs.amazon-neptune-mcp-server. Download a pre-built policy from policylayer.com/policies/aws-labs-amazon-neptune-mcp-server and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.