library_trigger_presentation

Trigger the first cue of a presentation in a library

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/library-trigger-presentation.md

What library_trigger_presentation does on Propresenter

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

This tool executes an action that causes observable external effects (starting a presentation with its first cue). While not destructive or financial, it triggers a real-world operation in ProPresenter 7 that an AI agent could misuse to disrupt presentations, alter their flow, or cause unintended playback sequences.

From the tool's definition Tool name contains 'trigger' and description states 'Trigger the first cue of a presentation in a library' — this initiates an external operation (presentation playback) whose effects depend on which presentation is selected.

Questions about library_trigger_presentation

What does the library_trigger_presentation tool do? +

Trigger the first cue of a presentation in a library. 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 library_trigger_presentation? +

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

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

Can I rate-limit library_trigger_presentation? +

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

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

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