Get detailed permissions for a specific doctype
AI agents call get_doctype_permissions 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 and queries permission configuration information for a doctype, which is a read-only operation. It has no side effects and does not modify, create, delete, or execute any operations. In the context of an ERP system with enterprise-grade permission controls and audit logging (as described in the server context), querying permissions is a fundamental Read operation.
From the tool's definition Tool name and description indicate retrieval of permission metadata: 'Get detailed permissions for a specific doctype'.
Attacks that exploit this kind of access
Get detailed permissions 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_permissions: 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_permissions 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_permissions 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_permissions. 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_permissions is provided by the ERPNext MCP Server MCP server (zero056/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 →