Get fields list for a specific DocType
AI agents call get_doctype_fields 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 queries and returns schema/field information for a DocType. It is a read-only operation that retrieves data (the field definitions) without side effects, creation, modification, deletion, code execution, or financial impact. The low severity reflects minimal blast radius even if misused—worst case, an agent learns the structure of documents but cannot act on them without other tools.
From the tool's definition Tool name 'get_doctype_fields' and description 'Get fields list for a specific DocType' indicate retrieval of metadata about document structure with no modification or execution of operations.
Attacks that exploit this kind of access
Get fields list for a specific DocType. 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_doctype_fields: 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_doctype_fields 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_doctype_fields 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_doctype_fields. 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_doctype_fields is provided by the ERPNext MCP Server MCP server (web3viralabs/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 →