High Risk →

playlists_focus_next

Focus the next playlist

How to control playlists_focus_next ↓

What playlists_focus_next does on Propresenter

AI agents invoke playlists_focus_next 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 playlists_focus_next needs a policy

This tool triggers an action in ProPresenter (focusing/navigating to the next playlist), which is an external operation that changes the state of the presentation software. It's not purely reading data, but rather executing a navigation/control action within the application.

From the tool's definition Focus the next playlist

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

How to control playlists_focus_next

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 playlists_focus_next:

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

playlists_focus_next 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 playlists_focus_next

What does the playlists_focus_next tool do? +

Focus the next 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 playlists_focus_next? +

Register the Propresenter MCP server in PolicyLayer and add a rule for playlists_focus_next: 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 playlists_focus_next? +

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

Can I rate-limit playlists_focus_next? +

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

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

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