AI agents call get_graph_info to retrieve information from Mcp Graph Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about graph structure (statistics, node/edge counts, etc.) with no side effects. It fits the 'Read' category as it queries data without creating, modifying, or deleting content. The low severity reflects that misuse would only expose data already in the graph, not enable destructive or financial harm.
From the tool's definition Tool name 'get_graph_info' and description 'Get graph statistics and info' indicate a query operation that retrieves metadata and statistics about an existing graph without modification.
Documented attack patterns abuse exactly the kind of access get_graph_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Graph Engine, and nothing reaches the server without passing your rules. This is the rule we recommend for get_graph_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_graph_info": {}
}
}get_graph_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get graph statistics and info. It is categorised as a Read tool in the Mcp Graph Engine MCP Server, which means it retrieves data without modifying state.
Register the Mcp Graph Engine MCP server in PolicyLayer and add a rule for get_graph_info: 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 Mcp Graph Engine. Nothing to install.
get_graph_info 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_info 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_info. 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_info is provided by the Mcp Graph Engine MCP server (utilitydelta/mcp-graph-engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Graph Engine, 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.
24 Mcp Graph Engine tools catalogued and risk-classified — across an index of 43,000+ MCP servers.