Query and visualize the thought graph. View the DAG structure, find paths, inspect branches, and get statistics.
AI agents call graph to retrieve information from Deep Thinker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'graph' tool is purely informational—it retrieves and displays internal thought graph data without creating, modifying, deleting, or executing anything. Querying a data structure, visualizing it, finding paths, and gathering statistics are all read operations that do not alter system state or trigger external actions.
From the tool's definition Tool description states: 'Query and visualize the thought graph. View the DAG structure, find paths, inspect branches, and get statistics.' All verbs (query, view, inspect, get) are read-only operations with no modification or side effects.
Documented attack patterns abuse exactly the kind of access graph gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Deep Thinker, and nothing reaches the server without passing your rules. This is the rule we recommend for graph:
{
"version": "1",
"default": "deny",
"tools": {
"graph": {}
}
} 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.
Query and visualize the thought graph. View the DAG structure, find paths, inspect branches, and get statistics. It is categorised as a Read tool in the Deep Thinker MCP Server, which means it retrieves data without modifying state.
Register the Deep Thinker MCP server in PolicyLayer and add a rule for 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 Deep Thinker. Nothing to install.
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 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 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.
graph is provided by the Deep Thinker MCP server (nachosystems/deep-thinker). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Deep Thinker, 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.
17 Deep Thinker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.