list_documents
List and search PandaDoc documents with filtering. Supports filtering by status, template, name/reference, tags, metadata, date ranges, and more. Returns compact summaries: id, name, status, dates. Status codes: 0=draft, 1=sent, 2=completed, 3=uploaded, 4=error, 5=viewed, 6=waiting_approval, 7=ap...
This record as markdown: /tools/freshdesk/list-documents.md
What list_documents does on Freshdesk
AI agents call list_documents 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 list_documents is rated Low
list_documents retrieves and searches existing document metadata without modifying, deleting, or executing operations. The tool only returns summaries of documents filtered by various criteria (status, template, name, tags, dates, etc.). This is a classic Read operation—no data is created, modified, or destroyed. Severity is low because viewing document lists poses minimal risk even if misused by an AI agent.
From the tool's definition Tool performs "List and search PandaDoc documents with filtering" and "Returns compact summaries: id, name, status, dates." These are query and retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs list_documents 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 list_documents, this is the rule to start with:
list_documents 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 list_documents call is checked against it from then on.
Questions about list_documents
List and search PandaDoc documents with filtering. Supports filtering by status, template, name/reference, tags, metadata, date ranges, and more. Returns compact summaries: id, name, status, dates. Status codes: 0=draft, 1=sent, 2=completed, 3=uploaded, 4=error, 5=viewed, 6=waiting_approval, 7=approved, 8=rejected, 9=waiting_pay, 10=paid, 11=voided, 12=declined RELATED TOOLS: - get_document_details: Get full details for a specific document - get_document_status: Quick status check by document ID. 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 list_documents: 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.
list_documents 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 list_documents 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 list_documents. 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.
list_documents 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