Low Risk

playback_get_state

Get current playback state including currentTime, volume, isPlaying, and isMuted

Part of the Opencut Controller MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call playback_get_state to retrieve information from Opencut Controller without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though playback_get_state only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

io-github-jxue0-opencut-controller.yaml
tools:
  playback_get_state:
    rules:
      - action: allow

See the full Opencut Controller policy for all 161 tools.

Tool Name playback_get_state
Category Read
Risk Level Low

View all 161 tools →

Agents calling read-class tools like playback_get_state have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the playback_get_state tool do? +

Get current playback state including currentTime, volume, isPlaying, and isMuted. It is categorised as a Read tool in the Opencut Controller MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on playback_get_state? +

Add a rule in your Intercept YAML policy under the tools section for playback_get_state. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Opencut Controller MCP server.

What risk level is playback_get_state? +

playback_get_state is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit playback_get_state? +

Yes. Add a rate_limit block to the playback_get_state rule in your Intercept 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 playback_get_state completely? +

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

playback_get_state is provided by the Opencut Controller MCP server (opencut-controller). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

Currently onboarding teams running MCP in production.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.

// REQUEST EARLY ACCESS

We're letting people in as fast as we can.

You're in the queue.

We'll be in touch as soon as we can let you in.