AI agents call stage_delete_layout to permanently remove resources in Propresenter — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a stage layout cannot be undone and removes data permanently. While the blast radius is confined to presentation layouts (not financial, not system-level), it represents clear data loss. Severity is high because accidental deletion of an actively-used stage layout in a live presentation environment could disrupt workflows, though it does not affect financial systems or core system integrity.
From the tool's definition Tool name explicitly uses 'delete' and description states 'Delete a specific stage layout' — this is an irreversible removal of a layout configuration in ProPresenter 7.
Documented attack patterns abuse exactly the kind of access stage_delete_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_delete_layout:
{
"version": "1",
"default": "deny",
"hide": [
"stage_delete_layout"
]
} stage_delete_layout disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete a specific stage layout. It is categorised as a Destructive tool in the Propresenter MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Propresenter MCP server in PolicyLayer and add a rule for stage_delete_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_delete_layout is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the stage_delete_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_delete_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_delete_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.