同步播放多个时间轴
AI agents invoke sync_timeline_playback to trigger actions in GSAP MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a playback action — triggering synchronized playback across multiple GSAP timelines. It is not merely reading or writing data, but actively executing an operation (playback control) that causes animations to run. This falls under Execute. Severity is medium because misuse could cause unintended UI behavior but has limited blast radius outside the browser/animation context.
From the tool's definition Tool name 'sync_timeline_playback' and description '同步播放多个时间轴' (synchronously play multiple timelines) indicates triggering/executing playback operations on multiple animation timelines.
Attacks that exploit this kind of access
同步播放多个时间轴. It is categorised as a Execute tool in the GSAP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the GSAP MCP Server MCP server in PolicyLayer and add a rule for sync_timeline_playback: 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 GSAP MCP Server. Nothing to install.
sync_timeline_playback is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the sync_timeline_playback 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_timeline_playback. 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_timeline_playback is provided by the GSAP MCP Server MCP server (lillard01/gsap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →