make_mapped_doc · ERPNext MCP Server MCP: Risk & Policy

WHAT IT DOES

What make_mapped_doc does on ERPNext MCP Server

AI agents use make_mapped_doc 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 make_mapped_doc needs a policy

The name 'make_mapped_doc' aligns with ERPNext's frappe.model.mapper pattern, which creates a new document derived/mapped from an existing one — a Write operation. However, the description is empty, significantly lowering confidence. It could potentially trigger workflows or submit documents depending on arguments, but Write is the most defensible base classification given the naming convention.

From the tool's definition Tool name 'make_mapped_doc' suggests creating a mapped/derived document from another document, which is a common ERPNext pattern (e.g., creating a Delivery Note from a Sales Order).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

make_mapped_doc Rate-limited

make_mapped_doc 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": {
    "make_mapped_doc": {
      "limits": [
        {
          "counter": "make_mapped_doc_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 make_mapped_doc

What does the make_mapped_doc tool do? +

make_mapped_doc. 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 make_mapped_doc? +

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

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

Can I rate-limit make_mapped_doc? +

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

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

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