update_document · ERPNext MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_document does on ERPNext MCP Server

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_document needs a policy

This tool creates or modifies data reversibly by updating existing documents in an ERP system. While the description is minimal, the server context (ERPNext document management) and sibling tools (cancel_document, create_document, delete_document) confirm this is a Write operation.

From the tool's definition Tool description: 'Update an existing document.' Server context indicates CRUD operations on ERPNext instances managing documents, inventory, and reports via REST API.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_document Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_document": {
      "limits": [
        {
          "counter": "update_document_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 update_document

What does the update_document tool do? +

Update an existing document. 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.

How do I enforce a policy on update_document? +

Register the ERPNext MCP Server MCP server in PolicyLayer and add a rule for update_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 update_document? +

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

Can I rate-limit update_document? +

Yes. Add a rate_limit block to the update_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 update_document completely? +

Set action: deny in the PolicyLayer policy for update_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 update_document? +

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

// THE FULL RECORD

update_document is one line of ERPNext MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →