read_graph_stream
Stream the knowledge graph with cursor pagination (500/page, updated_at DESC). Returns entities, relations, nextCursor.
This record as markdown: /tools/1999azzar-project-guardian-mcp-server/read-graph-stream.md
What read_graph_stream does on Project Guardian MCP
AI agents call read_graph_stream to retrieve information from Project Guardian MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_graph_stream is rated Low
Retrieves and queries knowledge graph data with no modifications, deletions, or side effects.
From the tool's definition Stream the knowledge graph with cursor pagination. Returns entities, relations.
Attacks that exploit this kind of access
The rule that runs read_graph_stream safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Project Guardian MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_graph_stream, this is the rule to start with:
read_graph_stream is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Project Guardian MCP, apply this rule, and every read_graph_stream call is checked against it from then on.
Questions about read_graph_stream
Stream the knowledge graph with cursor pagination (500/page, updated_at DESC). Returns entities, relations, nextCursor. It is categorised as a Read tool in the Project Guardian MCP MCP Server, which means it retrieves data without modifying state.
Register the Project Guardian MCP server in PolicyLayer and add a rule for read_graph_stream: 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 Project Guardian MCP. Nothing to install.
read_graph_stream 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_stream 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_stream. 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_stream is provided by the Project Guardian MCP server (1999azzar/project-guardian-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Project Guardian, and thousands of servers like it.
This server
Across the catalogue