This record as markdown: /tools/io-github-alxpark-propresenter-mcp/props-delete.md
What props_delete does on Propresenter
AI agents call props_delete 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.
Why props_delete is rated Critical
Deletion operations cannot be undone and permanently remove data from the system. This qualifies as Destructive rather than Write. The tool removes props from ProPresenter 7, which are presentation assets. While not at 'critical' severity (limited to a single prop rather than bulk deletion or system-critical data), the irreversible nature and potential impact on a live presentation warrants 'high' severity.
From the tool's definition Tool name is 'props_delete' with description 'Delete a specific prop'. The verb 'delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs props_delete 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 props_delete, this is the rule to start with:
props_delete is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Propresenter, apply this rule, and every props_delete call is checked against it from then on.
Questions about props_delete
Delete a specific prop. 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 props_delete: 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.
props_delete 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 props_delete 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 props_delete. 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.
props_delete 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.
Across the catalogue