get_file_metadata
Get custom metadata (SharePoint column values) for a file or folder. Returns all custom fields added by site administrators, such as Department, Status, Category, etc.
This record as markdown: /tools/freshdesk/get-file-metadata.md
What get_file_metadata does on Freshdesk
AI agents call get_file_metadata to retrieve information from Freshdesk without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_file_metadata is rated Low
This tool reads and returns metadata about files/folders (custom SharePoint column values) without creating, modifying, deleting, or executing anything. It is a straightforward data retrieval operation with minimal security risk, assuming the caller has appropriate file-access permissions.
From the tool's definition Tool description explicitly states 'Get custom metadata' and 'Returns all custom fields' — purely retrieves data with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs get_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 get_file_metadata, this is the rule to start with:
get_file_metadata is read-only, so it stays allowed. 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 get_file_metadata call is checked against it from then on.
Questions about get_file_metadata
Get custom metadata (SharePoint column values) for a file or folder. Returns all custom fields added by site administrators, such as Department, Status, Category, etc. It is categorised as a Read tool in the Freshdesk MCP Server, which means it retrieves data without modifying state.
Register the Freshdesk MCP server in PolicyLayer and add a rule for get_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.
get_file_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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