copy_file
Copy a file or folder to a new location.
This record as markdown: /tools/freshdesk/copy-file.md
What copy_file does on Freshdesk
AI agents use copy_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 copy_file is rated Medium
Copying files creates new data without deleting the original, making it a Write operation rather than Destructive. The severity is medium because copying files could create duplicate sensitive data, fill storage, or enable unauthorized data proliferation if the destination location is not properly controlled.
From the tool's definition Tool description states 'Copy a file or folder to a new location.' This creates a new instance of data in a new location, which is a reversible modification operation.
Attacks that exploit this kind of access
The rule that runs copy_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 copy_file, this is the rule to start with:
copy_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 copy_file call is checked against it from then on.
Questions about copy_file
Copy a file or folder to a new location. 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 copy_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.
copy_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 copy_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 copy_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.
copy_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