save_component_to_vault
Save a live TouchDesigner COMP as a reusable .tox component file inside the Obsidian vault (at <folder>/<name>.tox) and write a companion markdown note with frontmatter, a description, and load instructions — completing the build→parameterize→script→package-to-library loop. The saved .tox can lat...
This record as markdown: /tools/hybridlabor-api-aos/save-component-to-vault.md
What save_component_to_vault does on Aos
AI agents use save_component_to_vault to create or update resources in Aos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Aos environment.
Why save_component_to_vault is rated Medium
This tool creates and persists new data (a .tox component file and markdown metadata) to the file system. It is Write-category because it creates new files and modifies vault state reversibly—the saved components can be deleted or overwritten. It is not Execute because it does not run arbitrary code or scripts at runtime; it merely packages and serializes an existing component.
From the tool's definition Saves a live TouchDesigner COMP as a reusable .tox component file and writes a companion markdown note with frontmatter. Key verbs: 'Save', 'write'. Creates new files inside the Obsidian vault at a specified path.
Attacks that exploit this kind of access
The rule that runs save_component_to_vault 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 save_component_to_vault, this is the rule to start with:
save_component_to_vault stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 save_component_to_vault call is checked against it from then on.
Questions about save_component_to_vault
Save a live TouchDesigner COMP as a reusable .tox component file inside the Obsidian vault (at <folder>/<name>.tox) and write a companion markdown note with frontmatter, a description, and load instructions — completing the build→parameterize→script→package-to-library loop. The saved .tox can later be loaded back with manage_component (load action). Requires a configured TDMCP_VAULT_PATH. The target COMP must exist and be a COMP (not a non-COMP operator). It is categorised as a Write tool in the Aos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Aos MCP server in PolicyLayer and add a rule for save_component_to_vault: 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.
save_component_to_vault is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_component_to_vault 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 save_component_to_vault. 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.
save_component_to_vault 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