share_file
Create a sharing link for a file or folder.
This record as markdown: /tools/freshdesk/share-file.md
What share_file does on Freshdesk
AI agents use share_file 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 share_file is rated Medium
This tool creates or modifies sharing permissions/links for files or folders. While it does not delete data or execute arbitrary code, it does create new sharing artifacts (links) that alter the accessibility of data. This is a Write operation (creates reversible metadata/artifacts).
From the tool's definition Tool name and description: 'share_file' - 'Create a sharing link for a file or folder.' The action creates a new sharing link, which is a reversible modification to access controls and metadata.
Attacks that exploit this kind of access
The rule that runs share_file 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 share_file, this is the rule to start with:
share_file 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 share_file call is checked against it from then on.
Questions about share_file
Create a sharing link for a file or folder. 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 share_file: 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.
share_file 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 share_file 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 share_file. 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.
share_file 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