Low Risk

get_graph_status

Get the status of the currently configured Amazon Neptune graph.

How to control get_graph_status ↓

What get_graph_status does on Amazon EKS MCP Server

AI agents call get_graph_status to retrieve information from Amazon EKS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_graph_status needs a policy

This tool retrieves status information about an existing Neptune graph resource. The verb 'get' combined with 'status' is a clear read operation that queries state without altering data, executing code, or triggering external operations. The blast radius is minimal as it only returns information about graph state.

From the tool's definition Tool name 'get_graph_status' and description 'Get the status of the currently configured Amazon Neptune graph' indicate a retrieval operation with no modification or side effects.

Documented attack patterns abuse exactly the kind of access get_graph_status gives an agent:

How to control get_graph_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Amazon EKS MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_graph_status:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_graph_status": {}
  }
}

get_graph_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Amazon EKS MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_graph_status

What does the get_graph_status tool do? +

Get the status of the currently configured Amazon Neptune graph. It is categorised as a Read tool in the Amazon EKS MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_graph_status? +

Register the Amazon EKS MCP Server MCP server in PolicyLayer and add a rule for get_graph_status: 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 Amazon EKS MCP Server. Nothing to install.

What risk level is get_graph_status? +

get_graph_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_graph_status? +

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

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

get_graph_status is provided by the Amazon EKS MCP Server MCP server (awslabs.eks-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Amazon EKS MCP Server tool call.

Start from Amazon EKS MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.