trigger_previous_slide

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

Questions about trigger_previous_slide

What does the trigger_previous_slide tool do? +

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.

How do I enforce a policy on trigger_previous_slide? +

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.

What risk level is trigger_previous_slide? +

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

Can I rate-limit trigger_previous_slide? +

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.

How do I block trigger_previous_slide completely? +

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.

What MCP server provides trigger_previous_slide? +

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.

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