Trigger a specific audience look to make it live/current
AI agents invoke looks_trigger 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 performs an external operation (triggering a live presentation look) whose effects depend on which look is selected as an argument. It is not merely reading data (would be Read), nor creating/modifying persistent data structures (would be Write). It executes a command that changes the active presentation state.
From the tool's definition Tool name 'looks_trigger' and description 'Trigger a specific audience look to make it live/current' indicate an action that executes/applies a presentation look/view state in ProPresenter, changing what is displayed to the audience.
Documented attack patterns abuse exactly the kind of access looks_trigger 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 looks_trigger:
{
"version": "1",
"default": "deny",
"tools": {
"looks_trigger": {
"limits": [
{
"counter": "looks_trigger_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}looks_trigger 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 audience look to make it live/current. 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 looks_trigger: 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.
looks_trigger 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 looks_trigger 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 looks_trigger. 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.
looks_trigger 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.