audio_trigger_active_previous

Trigger the previous 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-previous.md

WHAT IT DOES

What audio_trigger_active_previous does on Propresenter

AI agents invoke audio_trigger_active_previous 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_active_previous is rated High

This tool executes an action (triggering previous track) in an external system (ProPresenter media player) whose effects depend on the runtime state of the playlist and audio system. It is not a simple read operation (doesn't just query state), nor does it create/modify persistent data. It has observable side effects on audio playback state, classifying it as Execute rather than Write.

From the tool's definition Tool name includes 'trigger' and description states 'Trigger the previous item in the active playlist', indicating it executes a command to control audio playback in ProPresenter 7.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs audio_trigger_active_previous 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_active_previous, this is the rule to start with:

audio_trigger_active_previous Rate-limited

audio_trigger_active_previous 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_active_previous": {
      "limits": [
        {
          "counter": "audio_trigger_active_previous_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_active_previous call is checked against it from then on.

FAQ

Questions about audio_trigger_active_previous

What does the audio_trigger_active_previous tool do? +

Trigger the previous 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_previous? +

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

audio_trigger_active_previous 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_previous? +

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

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

audio_trigger_active_previous 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 →