upload_document
Upload a PDF, DOCX, or RTF file to PandaDoc to create a new document. The file is uploaded and converted into an interactive PandaDoc document. After upload, the document status is
This record as markdown: /tools/freshdesk/upload-document.md
What upload_document does on Freshdesk
AI agents use upload_document 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 upload_document is rated Medium
This tool creates and modifies data (new PandaDoc documents) without irreversibility or deletion. While it transfers files to an external service, the core action is document creation/write. The blast radius is medium: misuse could flood PandaDoc with unwanted documents or expose sensitive file contents, but the operation is not inherently destructive or financially consequential.
From the tool's definition Tool performs 'Upload' action that 'create[s] a new document' in PandaDoc by converting file content into interactive format. The operation is reversible (document can be deleted post-upload) and results in creation of new data artifacts.
Attacks that exploit this kind of access
The rule that runs upload_document 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 upload_document, this is the rule to start with:
upload_document 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 upload_document call is checked against it from then on.
Questions about upload_document
Upload a PDF, DOCX, or RTF file to PandaDoc to create a new document. The file is uploaded and converted into an interactive PandaDoc document. After upload, the document status is. 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 upload_document: 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.
upload_document 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 upload_document 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 upload_document. 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.
upload_document 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