High Risk →

audio_focus_next_playlist

Focus the next audio playlist

How to control audio_focus_next_playlist ↓

What audio_focus_next_playlist does on Propresenter

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

High Risk

Why audio_focus_next_playlist needs a policy

This tool triggers an external operation in ProPresenter 7 (focusing/switching to the next audio playlist), which is an action with side effects on the running presentation software. It doesn't read data, write/create content, or destroy anything, but it does trigger a state change in an external application.

From the tool's definition Focus the next audio playlist

Documented attack patterns abuse exactly the kind of access audio_focus_next_playlist gives an agent:

How to control audio_focus_next_playlist

PolicyLayer is an MCP gateway — it sits between your AI agents and Propresenter, and nothing reaches the server without passing your rules. This is the rule we recommend for audio_focus_next_playlist:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "audio_focus_next_playlist": {
      "limits": [
        {
          "counter": "audio_focus_next_playlist_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

audio_focus_next_playlist 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.

  1. Create a free account and register Propresenter — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about audio_focus_next_playlist

What does the audio_focus_next_playlist tool do? +

Focus the next audio playlist. It is categorised as a Execute tool in the Propresenter MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on audio_focus_next_playlist? +

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

What risk level is audio_focus_next_playlist? +

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

Can I rate-limit audio_focus_next_playlist? +

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

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

audio_focus_next_playlist is provided by the Propresenter MCP server (@alxpark/propresenter-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Propresenter tool call.

Start from Propresenter, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

177 Propresenter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.