sync_external_clock
Lock the project tempo to a live source so beat-synced visuals follow the music.
This record as markdown: /tools/io-github-pantani-tdmcp/sync-external-clock.md
What sync_external_clock does on tdmcp — TouchDesigner MCP server
AI agents use sync_external_clock to create or update resources in tdmcp — TouchDesigner MCP server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your tdmcp — TouchDesigner MCP server environment.
Why sync_external_clock is rated Medium
This tool modifies the project's tempo/clock settings by synchronizing it to an external live source. It creates or modifies a project-level configuration (tempo locking) in a reversible way — it can be unlocked or changed again. No data is deleted, no code is executed arbitrarily, and no financial transaction occurs.
From the tool's definition Lock the project tempo to a live source so beat-synced visuals follow the music.
Attacks that exploit this kind of access
The rule that runs sync_external_clock safely
PolicyLayer is an MCP gateway: it sits between your AI agents and tdmcp — TouchDesigner MCP server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sync_external_clock, this is the rule to start with:
sync_external_clock 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 tdmcp — TouchDesigner MCP server, apply this rule, and every sync_external_clock call is checked against it from then on.
Questions about sync_external_clock
Lock the project tempo to a live source so beat-synced visuals follow the music. It is categorised as a Write tool in the tdmcp — TouchDesigner MCP server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the tdmcp — TouchDesigner MCP server MCP server in PolicyLayer and add a rule for sync_external_clock: 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 tdmcp — TouchDesigner MCP server. Nothing to install.
sync_external_clock 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 sync_external_clock 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 sync_external_clock. 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.
sync_external_clock is provided by the tdmcp — TouchDesigner MCP server MCP server (@dpantani/tdmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on tdmcp — TouchDesigner MCP server, and thousands of servers like it.
This server
Across the catalogue