Fetch a list of documents for a DocType with filtering and field selection. Use this for raw data tables like
AI agents call get_list_data 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.
This tool retrieves or queries data from ERPNext without causing any side effects. It performs filtering and field selection on existing documents but does not create, modify, delete, or execute any operations. This is a straightforward read operation with minimal risk if misused by an AI agent.
From the tool's definition Tool name 'get_list_data' and description 'Fetch a list of documents for a DocType with filtering and field selection' indicate data retrieval only. No modification, deletion, or execution capability mentioned.
Attacks that exploit this kind of access
Fetch a list of documents for a DocType with filtering and field selection. Use this for raw data tables like. 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 get_list_data: 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.
get_list_data 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_list_data 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_list_data. 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_list_data is provided by the ERPNext MCP Server MCP server (musab1khan/erpnext-mcp-server). 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 →