next_chapter · MCP Media Server MCP: Risk & Policy

WHAT IT DOES

What next_chapter does on MCP Media Server

AI agents invoke next_chapter to trigger actions in MCP Media 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.

WHY IT NEEDS A POLICY

Why next_chapter needs a policy

This tool executes a command against the media player to change playback position. While it is low-risk (reversible, local, no data loss), it qualifies as Execute rather than Write because it triggers an external operation (media player control) whose effect depends on the current playback state.

From the tool's definition Tool performs an action ('Jump to the next chapter') on a running media playback process, triggering a state change in an external system (the media player).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

next_chapter Rate-limited

next_chapter 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": {
    "next_chapter": {
      "limits": [
        {
          "counter": "next_chapter_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Media Server, so you can run agents against it safely.

FAQ

Questions about next_chapter

What does the next_chapter tool do? +

Jump to the next chapter or scene in the video. It is categorised as a Execute tool in the MCP Media Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on next_chapter? +

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

What risk level is next_chapter? +

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

Can I rate-limit next_chapter? +

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

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

next_chapter is provided by the MCP Media Server MCP server (neal3000/mcp_media_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.