This record as markdown: /tools/io-github-alxpark-propresenter-mcp/stage-get-message.md
What stage_get_message does on Propresenter
AI agents call stage_get_message to retrieve information from Propresenter without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why stage_get_message is rated Low
This tool queries and retrieves the current stage message from ProPresenter 7 without creating, modifying, or deleting any data. It is a simple GET operation that has no side effects on the system state. Therefore, it falls clearly into the Read category with low severity, as misuse would only expose informational data about presentation state.
From the tool's definition Tool name 'stage_get_message' and description 'Get the current stage message' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs stage_get_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_get_message, this is the rule to start with:
stage_get_message is read-only, so it stays allowed. 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_get_message call is checked against it from then on.
Questions about stage_get_message
Get the current stage message. It is categorised as a Read tool in the Propresenter MCP Server, which means it retrieves data without modifying state.
Register the Propresenter MCP server in PolicyLayer and add a rule for stage_get_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_get_message is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the stage_get_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_get_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_get_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.
This server
Across the catalogue