This record as markdown: /tools/hybridlabor-api-aos/bind-vault-text.md
What bind_vault_text does on Aos
AI agents use bind_vault_text 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 bind_vault_text is rated Medium
The tool creates a new Text DAT (data asset) in TouchDesigner, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. While it affects a visual design system, the modification is non-destructive and can be undone.
From the tool's definition Tool description states "CREATE a Text DAT in TouchDesigner" — the verb CREATE and the action of generating new data artifacts in TouchDesigner indicates data creation/modification.
Attacks that exploit this kind of access
The rule that runs bind_vault_text 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 bind_vault_text, this is the rule to start with:
bind_vault_text 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 bind_vault_text call is checked against it from then on.
Questions about bind_vault_text
CREATE a Text DAT in TouchDesigner whose. 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 bind_vault_text: 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.
bind_vault_text 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 bind_vault_text 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 bind_vault_text. 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.
bind_vault_text 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