get_document_details
Get full details for a PandaDoc document. Returns comprehensive data: recipients, fields, tokens, pricing, metadata, tags, linked objects, and more. Use this to inspect a document
This record as markdown: /tools/freshdesk/get-document-details.md
What get_document_details does on Freshdesk
AI agents call get_document_details 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_document_details is rated Low
This tool retrieves and queries document data without modifying it. However, the data returned includes sensitive information such as recipient details, pricing information, and linked objects, which could expose confidential business information if misused by a compromised AI agent. This elevates the severity from low to medium despite being a pure Read operation.
From the tool's definition The tool name is 'get_document_details' and the description states it 'Get full details for a PandaDoc document' and returns 'comprehensive data: recipients, fields, tokens, pricing, metadata, tags, linked objects, and more.' The verb 'Get' and the phrase 'to…
Attacks that exploit this kind of access
The rule that runs get_document_details 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_document_details, this is the rule to start with:
get_document_details 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_document_details call is checked against it from then on.
Questions about get_document_details
Get full details for a PandaDoc document. Returns comprehensive data: recipients, fields, tokens, pricing, metadata, tags, linked objects, and more. Use this to inspect a document. 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_document_details: 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_document_details 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_document_details 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_document_details. 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_document_details 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