list_documents
AI agents call list_documents to retrieve information from ERPNext MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'list_documents' indicates it retrieves or enumerates documents from the ERPNext system. Even without explicit description, the 'list' operation is universally non-destructive and returns data without modification. While confidence is slightly reduced due to the empty description, the naming convention and context strongly suggest a simple Read operation for querying/filtering documents.
From the tool's definition Tool name is 'list_documents' with no description provided. Based on the server's CRUD operation pattern and the name 'list', this follows the standard Read pattern of querying/retrieving data without side effects.
Attacks that exploit this kind of access
list_documents. It is categorised as a Read tool in the ERPNext MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ERPNext MCP Server 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 ERPNext MCP Server. 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 ERPNext MCP Server MCP server (yazelin/erpnext-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →