trigger_active_presentation

Retrigger the currently active presentation (starts from beginning)

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-active-presentation.md

What trigger_active_presentation does on Propresenter

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

This tool triggers/executes an external operation (presentation restart) whose effects depend on what presentation is currently active. It is not merely reading data (Read), nor is it creating/modifying persistent data (Write). Instead, it executes a command that causes ProPresenter to take an action.

From the tool's definition Tool name 'trigger_active_presentation' and description 'Retrigger the currently active presentation (starts from beginning)' indicate execution of a presentation restart operation.

Questions about trigger_active_presentation

What does the trigger_active_presentation tool do? +

Retrigger the currently active presentation (starts from beginning). 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_active_presentation? +

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

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

Can I rate-limit trigger_active_presentation? +

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

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

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