AI agents use stage_hide_message to create or update resources in Propresenter — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Propresenter environment.
This tool hides a stage message in ProPresenter 7, which is a reversible UI state change (the message can be shown again). It modifies display state but does not delete data or execute arbitrary code, making Write the appropriate category. Severity is low as it only affects presentation display.
From the tool's definition Hide the current stage message
Documented attack patterns abuse exactly the kind of access stage_hide_message 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 stage_hide_message:
{
"version": "1",
"default": "deny",
"tools": {
"stage_hide_message": {
"limits": [
{
"counter": "stage_hide_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}stage_hide_message stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Hide the current stage message. It is categorised as a Write tool in the Propresenter MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Propresenter MCP server in PolicyLayer and add a rule for stage_hide_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_hide_message is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the stage_hide_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_hide_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_hide_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.
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.