snap_timeline_time

Resolve a proposed timeline time against clip edges, markers, In/Out, playhead, and timeline start without editing.

SERVERCutpilot SOURCEHellotravisss/cutpilot

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/cutpilot/snap-timeline-time.md

WHAT IT DOES

What snap_timeline_time does on Cutpilot

AI agents invoke snap_timeline_time to trigger actions in Cutpilot. 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.

RISK

Why snap_timeline_time is rated High

snap_timeline_time triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs snap_timeline_time safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cutpilot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For snap_timeline_time, this is the rule to start with:

snap_timeline_time Rate-limited

snap_timeline_time stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "snap_timeline_time": {
      "limits": [
        {
          "counter": "snap_timeline_time_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about snap_timeline_time

What does the snap_timeline_time tool do? +

Resolve a proposed timeline time against clip edges, markers, In/Out, playhead, and timeline start without editing. It is categorised as a Execute tool in the Cutpilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on snap_timeline_time? +

Register the Cutpilot MCP server in PolicyLayer and add a rule for snap_timeline_time: 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 Cutpilot. Nothing to install.

What risk level is snap_timeline_time? +

snap_timeline_time is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit snap_timeline_time? +

Yes. Add a rate_limit block to the snap_timeline_time 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 snap_timeline_time completely? +

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

snap_timeline_time is provided by the Cutpilot MCP server (Hellotravisss/cutpilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cutpilot, and thousands of servers like it.

This server

All 219 Cutpilot tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →