library_lineage_graph
Read-only, offline tool that scans the vault library (Recipes, Shaders, Presets, Components, Setlists), extracts lineage frontmatter (parent_recipe, source_assets, remix_of, forked_from), and emits a lineage graph. Output as JSON (machine-consumable), Mermaid (paste into docs), or Graphviz DOT. N...
This record as markdown: /tools/hybridlabor-api-aos/library-lineage-graph.md
What library_lineage_graph does on Aos
AI agents call library_lineage_graph to retrieve information from Aos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why library_lineage_graph is rated Low
This tool performs data retrieval and analysis of existing library metadata. It extracts lineage frontmatter and outputs structured data in multiple formats (JSON, Mermaid, Graphviz DOT). There are no side effects, no code execution, no data modification, and no destructive operations. The explicit 'read-only' and 'offline' qualifiers confirm it is a passive query tool.
From the tool's definition 'Read-only, offline tool that scans the vault library... and emits a lineage graph.' The tool retrieves and queries metadata from local library files without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
The rule that runs library_lineage_graph safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Aos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For library_lineage_graph, this is the rule to start with:
library_lineage_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 Aos, apply this rule, and every library_lineage_graph call is checked against it from then on.
Questions about library_lineage_graph
Read-only, offline tool that scans the vault library (Recipes, Shaders, Presets, Components, Setlists), extracts lineage frontmatter (parent_recipe, source_assets, remix_of, forked_from), and emits a lineage graph. Output as JSON (machine-consumable), Mermaid (paste into docs), or Graphviz DOT. No TouchDesigner connection required. It is categorised as a Read tool in the Aos MCP Server, which means it retrieves data without modifying state.
Register the Aos MCP server in PolicyLayer and add a rule for library_lineage_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 Aos. Nothing to install.
library_lineage_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 library_lineage_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 library_lineage_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.
library_lineage_graph is provided by the Aos MCP server (@hybridlabor-api/aos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Aos, and thousands of servers like it.
This server
Across the catalogue