trigger_previous_slide
Trigger the previous cue in the current presentation
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/trigger-previous-slide.md
What trigger_previous_slide does on Propresenter
AI agents invoke trigger_previous_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.
Why trigger_previous_slide is rated High
This falls under Execute because it runs a command that triggers navigation within ProPresenter, an external application. While the action is reversible (users can navigate forward again), the tool directly controls presentation state on a remote system.
From the tool's definition The tool is described as 'Trigger the previous cue in the current presentation,' which directly triggers an external operation (slide navigation) in ProPresenter 7. It performs an action with observable effects rather than merely reading or writing data.
Attacks that exploit this kind of access
The rule that runs trigger_previous_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_previous_slide, this is the rule to start with:
trigger_previous_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Propresenter, apply this rule, and every trigger_previous_slide call is checked against it from then on.
Questions about trigger_previous_slide
Trigger the previous 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.
Register the Propresenter MCP server in PolicyLayer and add a rule for trigger_previous_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.
trigger_previous_slide is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trigger_previous_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.
Set action: deny in the PolicyLayer policy for trigger_previous_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.
trigger_previous_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.
More on Propresenter, and thousands of servers like it.
Across the catalogue