library_trigger_presentation_cue
Trigger a specific cue of a presentation in a library
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/library-trigger-presentation-cue.md
What library_trigger_presentation_cue does on Propresenter
AI agents invoke library_trigger_presentation_cue 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_cue is rated High
This tool executes a specific operation—triggering a presentation cue—which changes the state of the presentation software and affects what is displayed/played. While not destructive or financial, it represents an external operation whose effects depend on which cue is triggered. The blast radius is medium because triggering wrong cues could disrupt a live presentation, but it is reversible and doesn't damage data.
From the tool's definition Tool name contains 'trigger' and description states 'Trigger a specific cue of a presentation'. The term 'trigger' indicates execution of an action (playing a cue point in a presentation), not mere data retrieval.
Attacks that exploit this kind of access
The rule that runs library_trigger_presentation_cue 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 library_trigger_presentation_cue, this is the rule to start with:
library_trigger_presentation_cue 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 library_trigger_presentation_cue call is checked against it from then on.
Questions about library_trigger_presentation_cue
Trigger a specific 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.
Register the Propresenter MCP server in PolicyLayer and add a rule for library_trigger_presentation_cue: 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.
library_trigger_presentation_cue 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 library_trigger_presentation_cue 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 library_trigger_presentation_cue. 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.
library_trigger_presentation_cue 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