This record as markdown: /tools/cowork-bench/read-graph.md
What read_graph does on Cowork Bench
AI agents call read_graph to retrieve information from Cowork Bench 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 is rated Low
This tool retrieves data from a knowledge graph without creating, modifying, deleting, executing code, or triggering external operations. The verb 'read' and absence of any mutation or action language clearly place it in the Read category, which carries low severity since it only queries existing data.
From the tool's definition Tool name is 'read_graph' and description states 'Read the entire knowledge graph' — both explicitly indicate a retrieval operation with no modification or side effects.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs read_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Cowork Bench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_graph, this is the rule to start with:
read_graph 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 Cowork Bench, apply this rule, and every read_graph call is checked against it from then on.
Questions about read_graph
Read the entire knowledge graph. It is categorised as a Read tool in the Cowork Bench MCP Server, which means it retrieves data without modifying state.
Register the Cowork Bench 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 Cowork Bench. 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 Cowork Bench MCP server (0717376/cowork_bench). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Cowork Bench, and thousands of servers like it.
This server
Across the catalogue