Trigger a specific presentation by UUID, optionally starting at a specific slide index
AI agents invoke 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.
This tool executes an operation that changes the state of an external system (ProPresenter 7 presentation software), starting a presentation at a specified location. This is an Execute category tool because it triggers real-world effects in a presentation system that could disrupt ongoing services or meetings if invoked inappropriately.
From the tool's definition Tool name 'trigger_presentation' and description 'Trigger a specific presentation by UUID, optionally starting at a specific slide index' indicate execution of an external operation (triggering a presentation in ProPresenter 7) whose effects depend on the…
Documented attack patterns abuse exactly the kind of access trigger_presentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Propresenter, and nothing reaches the server without passing your rules. This is the rule we recommend for trigger_presentation:
{
"version": "1",
"default": "deny",
"tools": {
"trigger_presentation": {
"limits": [
{
"counter": "trigger_presentation_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}trigger_presentation 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.
Free to start. No card required.
Trigger a specific presentation by UUID, optionally starting at a specific slide index. 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_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.
trigger_presentation 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_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.
Set action: deny in the PolicyLayer policy for 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.
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.
Start from Propresenter, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
177 Propresenter tools catalogued and risk-classified — across an index of 43,000+ MCP servers.