Execute a standard ERPNext report (e.g.,
AI agents call get_report_data to retrieve information from ERPNext MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves or queries report data from the ERP system. Although 'Execute' appears in the description, it refers to executing a report query (read operation), not executing arbitrary code or system commands. No data is created, modified, or deleted. The tool's position among sibling tools (get_dashboard_data, get_sales_analytics, get_list_data) confirms it is a data retrieval tool.
From the tool's definition Tool name 'get_report_data' and description 'Execute a standard ERPNext report' indicate data retrieval without modification. Reports in ERPNext are read-only analytics outputs that do not alter system state.
Attacks that exploit this kind of access
Execute a standard ERPNext report (e.g.,. It is categorised as a Read tool in the ERPNext MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ERPNext MCP Server MCP server in PolicyLayer and add a rule for get_report_data: 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.
get_report_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_report_data 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.
Set action: deny in the PolicyLayer policy for get_report_data. 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.
get_report_data is provided by the ERPNext MCP Server MCP server (musab1khan/erpnext-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →