opus_delete_collection

Delete a clip collection.

SERVERFreshdesk SOURCE@mindstone-engineering/mcp-server-freshdesk
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/freshdesk/opus-delete-collection.md

What opus_delete_collection does on Freshdesk

AI agents call opus_delete_collection to permanently remove resources in Freshdesk, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why opus_delete_collection is rated Critical

This tool performs an irreversible operation that destroys data (a clip collection) and cannot be undone. Deletion operations are classified as Destructive. The high severity reflects that an AI agent misusing this tool could permanently remove user collections without recovery, impacting support workflows or data availability. High confidence due to explicit 'Delete' terminology in the tool name and description.

From the tool's definition Tool is named 'opus_delete_collection' with description 'Delete a clip collection.' The verb 'Delete' combined with 'collection' indicates irreversible data removal.

Questions about opus_delete_collection

What does the opus_delete_collection tool do? +

Delete a clip collection. It is categorised as a Destructive tool in the Freshdesk 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 opus_delete_collection? +

Register the Freshdesk MCP server in PolicyLayer and add a rule for opus_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 Freshdesk. Nothing to install.

What risk level is opus_delete_collection? +

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

Yes. Add a rate_limit block to the opus_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 opus_delete_collection completely? +

Set action: deny in the PolicyLayer policy for opus_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 opus_delete_collection? +

opus_delete_collection is provided by the Freshdesk MCP server (@mindstone-engineering/mcp-server-freshdesk). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Freshdesk, 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 Freshdesk'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.