trigger_next_slide

Trigger the next cue in the current presentation

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/trigger-next-slide.md

WHAT IT DOES

What trigger_next_slide does on Propresenter

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

This tool executes a command that modifies the state of a ProPresenter presentation (advancing to the next cue/slide). While not destructive (reversible via trigger_previous_slide), it is not a read operation and triggers external effects on a live presentation system, making it an Execute-category risk.

From the tool's definition Tool name 'trigger_next_slide' and description 'Trigger the next cue in the current presentation' indicate an action that advances a live presentation state.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

trigger_next_slide Rate-limited

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

FAQ

Questions about trigger_next_slide

What does the trigger_next_slide tool do? +

Trigger the next cue in the current presentation. 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 trigger_next_slide? +

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

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

Can I rate-limit trigger_next_slide? +

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

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

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