stage_show_message
Show a message on stage screens
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/stage-show-message.md
What stage_show_message does on Propresenter
AI agents invoke stage_show_message 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 stage_show_message is rated High
This tool triggers an external action (displaying a message on stage screens in ProPresenter), which constitutes an Execute operation affecting live presentation hardware. Misuse could disrupt live events or services being broadcast.
From the tool's definition "Show a message on stage screens" — triggers an external operation that causes visible output on stage display hardware
Attacks that exploit this kind of access
The rule that runs stage_show_message 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 stage_show_message, this is the rule to start with:
stage_show_message 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 stage_show_message call is checked against it from then on.
Questions about stage_show_message
Show a message on stage screens. 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 stage_show_message: 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.
stage_show_message 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 stage_show_message 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 stage_show_message. 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.
stage_show_message 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