get_bridge_logs

What get_bridge_logs does on tdmcp — TouchDesigner MCP server

AI agents call get_bridge_logs 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 get_bridge_logs is rated Low

This tool retrieves and queries diagnostic log information from a TouchDesigner project without creating, modifying, deleting, or executing any operations. It is a pure information retrieval operation, fitting the Read category. Severity is low because log data access poses minimal risk; it contains only debugging information about past errors and warnings, not sensitive credentials or control mechanisms.

From the tool's definition Tool name and description explicitly state 'Read-only: collect recent cook errors and warnings from the running TouchDesigner project for debugging.' The function walks the operator tree to retrieve log data with no modification or side effects.

The rule that runs get_bridge_logs 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 get_bridge_logs, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_bridge_logs": {}
  }
}

Questions about get_bridge_logs