sync_external_clock

Lock the project tempo to a live source so beat-synced visuals follow the music.

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

Questions about sync_external_clock

What does the sync_external_clock tool do? +

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.

How do I enforce a policy on sync_external_clock? +

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.

What risk level is sync_external_clock? +

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

Can I rate-limit sync_external_clock? +

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.

How do I block sync_external_clock completely? +

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.

What MCP server provides sync_external_clock? +

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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of tdmcp — TouchDesigner MCP server's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.