edit_dat_content
Surgically replace a substring inside a Text or Table DAT
This record as markdown: /tools/hybridlabor-api-aos/edit-dat-content.md
What edit_dat_content does on Aos
AI agents use edit_dat_content 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 edit_dat_content is rated Medium
This tool modifies the contents of data containers in TouchDesigner but does not delete, execute arbitrary code, or cause irreversible changes. The substring replacement is a surgical write operation that can be undone (e.g., by replacing back to original content). While it affects TouchDesigner project state, the scope is limited to a specific data container's content, justifying medium severity rather than high.
From the tool's definition 'Surgically replace a substring' indicates modification of existing data within a Text or Table DAT (data container in TouchDesigner). The tool creates or modifies data reversibly.
Attacks that exploit this kind of access
The rule that runs edit_dat_content 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 edit_dat_content, this is the rule to start with:
edit_dat_content 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 edit_dat_content call is checked against it from then on.
Questions about edit_dat_content
Surgically replace a substring inside a Text or Table DAT. 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 edit_dat_content: 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.
edit_dat_content 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 edit_dat_content 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 edit_dat_content. 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.
edit_dat_content 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