Get the status of the currently configured Amazon Neptune graph.
AI agents call get_graph_status to retrieve information from AWS IoT SiteWise MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves status information about an existing Neptune graph resource. It performs no modification, execution of code, deletion, or financial transaction. The operation is a simple data retrieval that returns the current state of a resource without altering it.
From the tool's definition Tool name is 'get_graph_status' and description states 'Get the status of the currently configured Amazon Neptune graph.' The verb 'Get' and 'status' are unambiguous indicators of a read-only query operation with no side effects.
Attacks that exploit this kind of access
Get the status of the currently configured Amazon Neptune graph. It is categorised as a Read tool in the AWS IoT SiteWise MCP Server MCP Server, which means it retrieves data without modifying state.
Register the AWS IoT SiteWise 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 AWS IoT SiteWise MCP Server. Nothing to install.
get_graph_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
get_graph_status is provided by the AWS IoT SiteWise MCP Server MCP server (awslabs.aws-iot-sitewise-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.