RETRIEVE the complete KNOWLEDGE GRAPH with all entities and relationships for a project. Returns comprehensive view of the entire network structure. Can be large for projects with many entities.
AI agents call read_graph to retrieve information from KnowledgeGraph MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing knowledge graph data without creating, modifying, or deleting any information. It is a straightforward data retrieval operation with no side effects.
From the tool's definition Tool name 'read_graph' and description 'RETRIEVE the complete KNOWLEDGE GRAPH with all entities and relationships' and 'Returns comprehensive view' indicate data retrieval with no modification.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access read_graph gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and KnowledgeGraph MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for read_graph:
{
"version": "1",
"default": "deny",
"tools": {
"read_graph": {}
}
} read_graph 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.
RETRIEVE the complete KNOWLEDGE GRAPH with all entities and relationships for a project. Returns comprehensive view of the entire network structure. Can be large for projects with many entities. It is categorised as a Read tool in the KnowledgeGraph MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KnowledgeGraph MCP Server MCP server in PolicyLayer and add a rule for read_graph: 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 KnowledgeGraph MCP Server. Nothing to install.
read_graph 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 read_graph 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 read_graph. 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.
read_graph is provided by the KnowledgeGraph MCP Server MCP server (n-r-w/knowledgegraph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from KnowledgeGraph 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.
11 KnowledgeGraph MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.