Critical Risk →

props_delete_collection

Delete a specific prop collection

Single-target operation

Part of the Propresenter MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents may call props_delete_collection to permanently remove or destroy resources in Propresenter. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. Intercept blocks destructive tools by default and requires explicit human approval before enabling them.

Without a policy, an AI agent could call props_delete_collection in a loop, permanently destroying resources in Propresenter. There is no undo for destructive operations. Intercept blocks this tool by default and only allows it when a human explicitly approves the action.

Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.

io-github-alxpark-propresenter-mcp.yaml
tools:
  props_delete_collection:
    rules:
      - action: deny
        reason: "Blocked by default — enable with approval"

See the full Propresenter policy for all 177 tools.

Tool Name props_delete_collection
Category Destructive
Risk Level Critical

View all 177 tools →

Agents calling destructive-class tools like props_delete_collection have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Destructive risk category across the catalogue. The same policy patterns (deny, require_approval) apply to each.

props_delete_collection is one of the critical-risk operations in Propresenter. For the full severity-focused view — only the critical-risk tools with their recommended policies — see the breakdown for this server, or browse all critical-risk tools across every MCP server.

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? +

Add a rule in your Intercept YAML policy under the tools section for props_delete_collection. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Propresenter MCP server.

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 Intercept 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 Intercept 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). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.