create_shared_memory_bridge
Create a Shared Memory In/Out TOP/CHOP for zero-copy IPC with another app on the same host (Notch, Unity, Unreal, custom tools). Pick direction (
This record as markdown: /tools/hybridlabor-api-aos/create-shared-memory-bridge.md
What create_shared_memory_bridge does on Aos
AI agents use create_shared_memory_bridge 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 create_shared_memory_bridge is rated Medium
This tool creates shared memory bridge objects (nodes/operators) in TouchDesigner to enable inter-process communication. It is a Write operation because it creates new data pathways/nodes. The severity is medium because misconfiguration could expose shared memory to unintended processes or disrupt IPC with connected applications, but it doesn't directly execute arbitrary code or destroy data.
From the tool's definition Create a Shared Memory In/Out TOP/CHOP for zero-copy IPC with another app
Attacks that exploit this kind of access
The rule that runs create_shared_memory_bridge 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 create_shared_memory_bridge, this is the rule to start with:
create_shared_memory_bridge 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 create_shared_memory_bridge call is checked against it from then on.
Questions about create_shared_memory_bridge
Create a Shared Memory In/Out TOP/CHOP for zero-copy IPC with another app on the same host (Notch, Unity, Unreal, custom tools). Pick direction (. 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 create_shared_memory_bridge: 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.
create_shared_memory_bridge 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 create_shared_memory_bridge 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 create_shared_memory_bridge. 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.
create_shared_memory_bridge 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