status_set_stage
Set the configuration of stage screens
This record as markdown: /tools/io-github-alxpark-propresenter-mcp/status-set-stage.md
What status_set_stage does on Propresenter
AI agents use status_set_stage 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.
Why status_set_stage is rated Medium
This tool modifies the configuration of stage screens in ProPresenter 7. It creates or updates settings (configuration), which is a reversible write operation. Misuse could disrupt live presentation stage displays.
From the tool's definition Set the configuration of stage screens
Attacks that exploit this kind of access
The rule that runs status_set_stage 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 status_set_stage, this is the rule to start with:
status_set_stage 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Propresenter, apply this rule, and every status_set_stage call is checked against it from then on.
Questions about status_set_stage
Set the configuration of stage screens. 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 status_set_stage: 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.
status_set_stage 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 status_set_stage 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 status_set_stage. 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.
status_set_stage 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