audio_trigger_active_next

Trigger the next item in the active 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-active-next.md

What audio_trigger_active_next does on Propresenter

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

Why audio_trigger_active_next is rated High

This tool executes a command that controls audio playback in ProPresenter 7, causing a state change in an external system (advancing to next audio item). While not destructive or financially harmful, it is an Execute-category action because it triggers an operation with real-world effects.

From the tool's definition Tool name contains 'trigger' and description states 'Trigger the next item in the active playlist' — this invokes an external operation (audio playback control) whose effects depend on system state.

Questions about audio_trigger_active_next

What does the audio_trigger_active_next tool do? +

Trigger the next item in the active 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_active_next? +

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

audio_trigger_active_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_active_next? +

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

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

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

More on Propresenter, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Propresenter's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.