AI agents call stage_get_screen_layout to retrieve information from Propresenter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration or state information about a stage screen layout. It performs a read-only query operation with no capability to modify, execute, delete, or perform financial operations. The blast radius of misuse is minimal—an attacker could only learn about the current layout configuration without causing harm.
From the tool's definition Tool name is 'stage_get_screen_layout' with description 'Get the layout for a specific stage screen'. The verb 'get' indicates data retrieval with no modification or side effects.
Documented attack patterns abuse exactly the kind of access stage_get_screen_layout 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_get_screen_layout:
{
"version": "1",
"default": "deny",
"tools": {
"stage_get_screen_layout": {}
}
}stage_get_screen_layout is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get the layout for a specific stage screen. 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_screen_layout: 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_screen_layout 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_screen_layout 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_screen_layout. 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_screen_layout 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.