High Risk →

run_gremlin_query

Executes the provided Tinkerpop Gremlin against the graph.

Accepts freeform code/query input (query)

Part of the AWS Labs Amazon Neptune MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents invoke run_gremlin_query to trigger processes or run actions in AWS Labs Amazon Neptune MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

run_gremlin_query can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

aws-labs-amazon-neptune-mcp-server.yaml
tools:
  run_gremlin_query:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full AWS Labs Amazon Neptune MCP Server policy for all 4 tools.

Tool Name run_gremlin_query
Category Execute
Risk Level High

Agents calling execute-class tools like run_gremlin_query have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

run_gremlin_query is one of the high-risk operations in AWS Labs Amazon Neptune MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the run_gremlin_query tool do? +

Executes the provided Tinkerpop Gremlin against the graph.. It is categorised as a Execute tool in the AWS Labs Amazon Neptune 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 run_gremlin_query? +

Add a rule in your Intercept YAML policy under the tools section for run_gremlin_query. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the AWS Labs Amazon Neptune MCP Server MCP server.

What risk level is run_gremlin_query? +

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

Can I rate-limit run_gremlin_query? +

Yes. Add a rate_limit block to the run_gremlin_query rule in your Intercept 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 run_gremlin_query completely? +

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

run_gremlin_query is provided by the AWS Labs Amazon Neptune MCP Server MCP server (awslabs.amazon-neptune-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.