props_delete_collection

Delete a specific prop collection

SERVERPropresenter SOURCE@alxpark/propresenter-mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alxpark-propresenter-mcp/props-delete-collection.md

What props_delete_collection does on Propresenter

AI agents call props_delete_collection 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_collection is rated Critical

The tool performs an irreversible deletion operation on prop collections in ProPresenter 7. Even though the blast radius is limited to presentation props rather than critical system data, deletion of collections cannot be undone and represents loss of user work. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.'

From the tool's definition Tool name contains 'delete' and description states 'Delete a specific prop collection' — this is an irreversible removal of data.

Questions about props_delete_collection

What does the props_delete_collection tool do? +

Delete a specific prop collection. 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.

How do I enforce a policy on props_delete_collection? +

Register the Propresenter MCP server in PolicyLayer and add a rule for props_delete_collection: 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.

What risk level is props_delete_collection? +

props_delete_collection is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit props_delete_collection? +

Yes. Add a rate_limit block to the props_delete_collection 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.

How do I block props_delete_collection completely? +

Set action: deny in the PolicyLayer policy for props_delete_collection. 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.

What MCP server provides props_delete_collection? +

props_delete_collection 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Propresenter's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.