audio_trigger_focused_next

Trigger the next item in the focused playlist

SERVERPropresenter SOURCE@alxpark/propresenter-mcp

High RISK CLASS

Category Execute

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-alxpark-propresenter-mcp/audio-trigger-focused-next.md

WHAT IT DOES

What audio_trigger_focused_next does on Propresenter

AI agents invoke audio_trigger_focused_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.

RISK

Why audio_trigger_focused_next is rated High

This tool executes a command that triggers audio playback progression in ProPresenter 7. While not destructive or financial, triggering playlist advancement is a state-changing operation with real-world effects (audio output changes). The tool depends on runtime state (focused playlist) and the argument (next item), making the outcome contingent on current system state.

From the tool's definition Tool name contains 'trigger' and description states 'Trigger the next item in the focused playlist' — this initiates an action (advancing playback) with external effects on audio playback state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs audio_trigger_focused_next safely

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

audio_trigger_focused_next Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "audio_trigger_focused_next": {
      "limits": [
        {
          "counter": "audio_trigger_focused_next_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Propresenter, apply this rule, and every audio_trigger_focused_next call is checked against it from then on.

FAQ

Questions about audio_trigger_focused_next

What does the audio_trigger_focused_next tool do? +

Trigger the next item in the focused 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_trigger_focused_next? +

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

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

Can I rate-limit audio_trigger_focused_next? +

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

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

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

KEEP EXPLORING

More on Propresenter, and thousands of servers like it.

This server

All 177 Propresenter tools → High-risk tools on this server →

Across the catalogue

qt_trigger_action on Qt → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →