opus_share_project
Update the sharing visibility of an OpusClip project.
This record as markdown: /tools/freshdesk/opus-share-project.md
What opus_share_project does on Freshdesk
AI agents use opus_share_project 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_share_project is rated Medium
This tool modifies project metadata (sharing visibility settings) in a reversible manner. While it affects access controls, it does not delete data, execute arbitrary operations, or move money. The change can be undone by updating visibility settings again.
From the tool's definition Tool description states 'Update the sharing visibility of an OpusClip project', indicating modification of project settings/permissions.
Attacks that exploit this kind of access
The rule that runs opus_share_project 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_share_project, this is the rule to start with:
opus_share_project 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_share_project call is checked against it from then on.
Questions about opus_share_project
Update the sharing visibility of an OpusClip project. 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_share_project: 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_share_project 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_share_project 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_share_project. 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_share_project 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