update_file_metadata
Update custom metadata (SharePoint column values) for a file or folder. Set values for custom fields like Department, Status, Category, etc.
This record as markdown: /tools/freshdesk/update-file-metadata.md
What update_file_metadata does on Freshdesk
AI agents use update_file_metadata 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 update_file_metadata is rated Medium
The tool creates or modifies data (metadata fields) without deleting or executing code. This is a Write operation because changes to metadata are reversible and don't destroy data. Severity is medium because unauthorized metadata changes could impact document organization, access controls, or compliance tracking, but the impact is limited to metadata rather than core file content or destructive operations.
From the tool's definition Tool performs 'Update custom metadata' and 'Set values for custom fields' on files or folders, modifying SharePoint column values. These are reversible write operations.
Attacks that exploit this kind of access
The rule that runs update_file_metadata 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 update_file_metadata, this is the rule to start with:
update_file_metadata 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 update_file_metadata call is checked against it from then on.
Questions about update_file_metadata
Update custom metadata (SharePoint column values) for a file or folder. Set values for custom fields like Department, Status, Category, etc. 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 update_file_metadata: 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.
update_file_metadata 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 update_file_metadata 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 update_file_metadata. 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.
update_file_metadata 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