submit_document · ERPNext MCP Server MCP: Risk & Policy

WHAT IT DOES

What submit_document does on ERPNext MCP Server

AI agents invoke submit_document to trigger actions in ERPNext MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why submit_document needs a policy

Submitting a document in ERPNext triggers a workflow state transition that locks the document and can initiate downstream financial and inventory effects (e.g., posting ledger entries, stock movements). This is an irreversible state change that goes beyond a simple write, making it Execute-level.

From the tool's definition Submit a submittable document (e.g. Sales Invoice)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_document Rate-limited

submit_document stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "submit_document": {
      "limits": [
        {
          "counter": "submit_document_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ERPNext MCP Server, so you can run agents against it safely.

FAQ

Questions about submit_document

What does the submit_document tool do? +

Submit a submittable document (e.g. Sales Invoice). It is categorised as a Execute tool in the ERPNext MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on submit_document? +

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.

What risk level is submit_document? +

submit_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit submit_document? +

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.

How do I block submit_document completely? +

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.

What MCP server provides submit_document? +

submit_document 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.