document_network
Document an EXISTING network: read its nodes and connections and return a readable map — counts by operator family and type, plus a Mermaid flowchart of the data flow you can paste into docs. Unlike plan_visual (which plans from a description), this describes what
This record as markdown: /tools/io-github-pantani-tdmcp/document-network.md
What document_network does on tdmcp — TouchDesigner MCP server
AI agents call document_network to retrieve information from tdmcp — TouchDesigner MCP server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why document_network is rated Low
This tool performs introspection and documentation of existing TouchDesigner networks without modifying them. It retrieves data (node counts, connections, flowchart representation) for analysis and documentation purposes. There are no side effects, modifications, code execution, deletions, or financial operations involved. The blast radius of misuse is minimal—it only reads and exports existing network information.
From the tool's definition The tool 'document_network' is described as reading and analyzing an existing network: 'read its nodes and connections and return a readable map', 'counts by operator family and type', and 'Mermaid flowchart'.
Attacks that exploit this kind of access
The rule that runs document_network safely
PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For document_network, this is the rule to start with:
document_network 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 tdmcp — TouchDesigner MCP server, apply this rule, and every document_network call is checked against it from then on.
Questions about document_network
Document an EXISTING network: read its nodes and connections and return a readable map — counts by operator family and type, plus a Mermaid flowchart of the data flow you can paste into docs. Unlike plan_visual (which plans from a description), this describes what. It is categorised as a Read tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it retrieves data without modifying state.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for document_network: 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 tdmcp — TouchDesigner MCP server. Nothing to install.
document_network 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 document_network 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 document_network. 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.
document_network is provided by the tdmcp — TouchDesigner MCP server MCP server (@dpantani/tdmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
This server
Across the catalogue