Medium Risk

erpnext_doc_submit

Submit any ERPNext document (changes status from Draft to Submitted). Applies to submittable DocTypes like Sales Order, Purchase Order, Sales Invoice, etc. Calls frappe.client.submit via the Frappe method API.

Part of the Mcp Erpnext MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@casys/mcp-erpnext Write Risk 2/5

AI agents use erpnext_doc_submit to create or modify resources in Mcp Erpnext. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call erpnext_doc_submit repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcp Erpnext.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

mcp-erpnext.yaml
tools:
  erpnext_doc_submit:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Mcp Erpnext policy for all 120 tools.

Tool Name erpnext_doc_submit
Category Write
Risk Level Medium

View all 120 tools →

Agents calling write-class tools like erpnext_doc_submit have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the erpnext_doc_submit tool do? +

Submit any ERPNext document (changes status from Draft to Submitted). Applies to submittable DocTypes like Sales Order, Purchase Order, Sales Invoice, etc. Calls frappe.client.submit via the Frappe method API.. It is categorised as a Write tool in the Mcp Erpnext MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on erpnext_doc_submit? +

Add a rule in your Intercept YAML policy under the tools section for erpnext_doc_submit. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Mcp Erpnext MCP server.

What risk level is erpnext_doc_submit? +

erpnext_doc_submit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit erpnext_doc_submit? +

Yes. Add a rate_limit block to the erpnext_doc_submit rule in your Intercept 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 erpnext_doc_submit completely? +

Set action: deny in the Intercept policy for erpnext_doc_submit. 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 erpnext_doc_submit? +

erpnext_doc_submit is provided by the Mcp Erpnext MCP server (@casys/mcp-erpnext). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Mcp Erpnext

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.