opus_add_clip_to_collection
Add a clip to an existing collection.
This record as markdown: /tools/freshdesk/opus-add-clip-to-collection.md
What opus_add_clip_to_collection does on Freshdesk
AI agents use opus_add_clip_to_collection to create or update resources in Freshdesk, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Freshdesk environment.
Why opus_add_clip_to_collection is rated Medium
This tool modifies data by adding a clip to a collection. This is a write operation because it creates or updates an association/relationship. The blast radius is medium because misuse could result in improper organization of clips or false associations, but the action is reversible and does not destroy data or execute arbitrary code.
From the tool's definition Tool description states 'Add a clip to an existing collection' - the verb 'Add' indicates creation or modification of data. The action creates a new association between a clip and a collection, which is reversible (the clip can be removed later).
Attacks that exploit this kind of access
The rule that runs opus_add_clip_to_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_add_clip_to_collection, this is the rule to start with:
opus_add_clip_to_collection stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Freshdesk, apply this rule, and every opus_add_clip_to_collection call is checked against it from then on.
Questions about opus_add_clip_to_collection
Add a clip to an existing collection. It is categorised as a Write tool in the Freshdesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Freshdesk MCP server in PolicyLayer and add a rule for opus_add_clip_to_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_add_clip_to_collection is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the opus_add_clip_to_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_add_clip_to_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_add_clip_to_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.
This server
Across the catalogue