sync_timecode

Wire an external SMPTE/MTC/LTC/OSC timecode source into the TouchDesigner timeline. Creates the input op + Math CHOP normaliser + Null CHOP

SERVERAos SOURCE@hybridlabor-api/aos

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/hybridlabor-api-aos/sync-timecode.md

WHAT IT DOES

What sync_timecode does on Aos

AI agents use sync_timecode 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.

RISK

Why sync_timecode is rated Medium

This tool creates new operators (nodes) and wires them into the TouchDesigner network to connect an external timecode source. It is a Write operation — it modifies the project by creating and linking components — but it does not execute arbitrary code, delete data, or involve financial transactions. Misuse could disrupt timeline synchronization across a live visual system, hence medium severity.

From the tool's definition Wire an external SMPTE/MTC/LTC/OSC timecode source into the TouchDesigner timeline. Creates the input op + Math CHOP normaliser + Null CHOP

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sync_timecode 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 sync_timecode, this is the rule to start with:

sync_timecode Rate-limited

sync_timecode 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sync_timecode": {
      "limits": [
        {
          "counter": "sync_timecode_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Aos, apply this rule, and every sync_timecode call is checked against it from then on.

FAQ

Questions about sync_timecode

What does the sync_timecode tool do? +

Wire an external SMPTE/MTC/LTC/OSC timecode source into the TouchDesigner timeline. Creates the input op + Math CHOP normaliser + Null CHOP. 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.

How do I enforce a policy on sync_timecode? +

Register the Aos MCP server in PolicyLayer and add a rule for sync_timecode: 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.

What risk level is sync_timecode? +

sync_timecode is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit sync_timecode? +

Yes. Add a rate_limit block to the sync_timecode 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.

How do I block sync_timecode completely? +

Set action: deny in the PolicyLayer policy for sync_timecode. 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.

What MCP server provides sync_timecode? +

sync_timecode 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.

KEEP EXPLORING

More on Aos, and thousands of servers like it.

This server

All 719 Aos tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →