run_report · ERPNext MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_report does on ERPNext MCP Server

AI agents invoke run_report 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 run_report needs a policy

Reports in ERP systems can range from simple reads to complex computations that may trigger side effects (e.g., auto-generated documents, data exports, or calculations affecting business logic). Execution of an arbitrary report without input validation could allow an AI agent to run resource-intensive or sensitive reports.

From the tool's definition Tool description states 'Execute an ERPNext report' — the verb 'Execute' indicates active computation/processing of a report, which is a query or procedural operation triggered on external system (ERPNext instance).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_report Rate-limited

run_report 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": {
    "run_report": {
      "limits": [
        {
          "counter": "run_report_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 run_report

What does the run_report tool do? +

Execute an ERPNext report. 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 run_report? +

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

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

Can I rate-limit run_report? +

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

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

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