audio_trigger_focused_next

THE RISK

High Risk

Why audio_trigger_focused_next needs a policy

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.

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

POLICY

How to control audio_trigger_focused_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 audio_trigger_focused_next:

policy.json

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

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.

Create a free account and register Propresenter — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Propresenter tools

Destructive clear_layer Clear a specific layer (audio, props, messages, announcements, slide, media, video_input) Destructive messages_delete Delete a specific message Destructive props_clear Clear a specific prop from display Destructive props_delete Delete a specific prop Destructive props_delete_collection Delete a specific prop collection Destructive stage_delete_layout Delete a specific stage layout Execute clear_trigger_group Trigger a specific clear group Execute props_pause_auto_clear Pause auto-clear for a specific prop

All 177 Propresenter tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Propresenter → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

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.

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.

CHECK YOUR STACK →