Submit a document (set docstatus to 1). Only works on submittable doctypes. Submitted documents can only be cancelled, not reverted to draft.
AI agents use submit_document to create or update resources in ERPNext MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ERPNext MCP Server environment.
Submitting a document in ERPNext transitions it to a locked state that cannot be reverted to draft — only cancelled. This is a significant state change that triggers downstream effects (inventory movements, accounting entries, etc.) and is effectively irreversible in the normal workflow sense.
From the tool's definition Submit a document (set docstatus to 1). Submitted documents can only be cancelled, not reverted to draft.
Documented attack patterns abuse exactly the kind of access submit_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ERPNext MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for submit_document:
{
"version": "1",
"default": "deny",
"tools": {
"submit_document": {
"limits": [
{
"counter": "submit_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}submit_document stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Submit a document (set docstatus to 1). Only works on submittable doctypes. Submitted documents can only be cancelled, not reverted to draft. It is categorised as a Write tool in the ERPNext MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ERPNext MCP Server MCP server in PolicyLayer and add a rule for submit_document: 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.
submit_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the submit_document 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 submit_document. 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.
submit_document is provided by the ERPNext MCP Server MCP server (rakeshgangwar/erpnext-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 11 ERPNext MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
11 ERPNext MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.