opus_remove_clip_from_collection
Remove a clip from a collection.
This record as markdown: /tools/freshdesk/opus-remove-clip-from-collection.md
What opus_remove_clip_from_collection does on Freshdesk
AI agents call opus_remove_clip_from_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_remove_clip_from_collection is rated Critical
Removing a clip from a collection deletes the association or the clip itself, which is typically not reversible. This falls under the Destructive category as data is permanently removed. Severity is high because an AI agent could accidentally remove important media clips from collections, potentially causing data loss.
From the tool's definition 'Remove a clip from a collection' — removal of content from a collection is an irreversible destructive action
Attacks that exploit this kind of access
The rule that runs opus_remove_clip_from_collection safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Freshdesk, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For opus_remove_clip_from_collection, this is the rule to start with:
opus_remove_clip_from_collection 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 Freshdesk, apply this rule, and every opus_remove_clip_from_collection call is checked against it from then on.
Questions about opus_remove_clip_from_collection
Remove a clip from a 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.
Register the Freshdesk MCP server in PolicyLayer and add a rule for opus_remove_clip_from_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.
opus_remove_clip_from_collection 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 opus_remove_clip_from_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.
Set action: deny in the PolicyLayer policy for opus_remove_clip_from_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.
opus_remove_clip_from_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.
Across the catalogue