toggle_cue_point

Set or delete a cue point at the current playback position.

SERVERLivepilot SOURCElivepilot

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-dreamrec-livepilot/toggle-cue-point.md

WHAT IT DOES

What toggle_cue_point does on Livepilot

AI agents use toggle_cue_point to create or update resources in Livepilot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livepilot environment.

RISK

Why toggle_cue_point is rated Medium

The tool primarily writes data by setting a cue point, but also has a delete capability. Since cue points are lightweight markers that can typically be re-added, this is best classified as Write rather than Destructive. The delete aspect is reversible in practice (cue points can be re-created), so Write is the most appropriate category.

From the tool's definition 'Set or delete a cue point at the current playback position' — the tool can both create (set) or remove (delete) a cue point

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs toggle_cue_point safely

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

toggle_cue_point Rate-limited

toggle_cue_point 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": {
    "toggle_cue_point": {
      "limits": [
        {
          "counter": "toggle_cue_point_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 Livepilot, apply this rule, and every toggle_cue_point call is checked against it from then on.

FAQ

Questions about toggle_cue_point

What does the toggle_cue_point tool do? +

Set or delete a cue point at the current playback position. It is categorised as a Write tool in the Livepilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on toggle_cue_point? +

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

What risk level is toggle_cue_point? +

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

Can I rate-limit toggle_cue_point? +

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

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

toggle_cue_point is provided by the Livepilot MCP server (livepilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Livepilot, and thousands of servers like it.

This server

All 474 Livepilot tools →

Across the catalogue

The MCP Attack Database →

Guides

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