run_method
AI agents invoke run_method 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.
Although the description is empty, the tool name 'run_method' combined with the server context (ERPNext with CRUD, workflows, and document management) indicates this executes server-side methods whose effects depend on which method is invoked.
From the tool's definition Tool name 'run_method' on an ERPNext MCP server that supports full CRUD operations and document workflows. The sibling tools include create_document, delete_document, and cancel_document, indicating this server manages critical business data.
Attacks that exploit this kind of access
run_method. 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.
Register the ERPNext MCP Server MCP server in PolicyLayer and add a rule for run_method: 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.
run_method is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_method 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 run_method. 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.
run_method 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.
run_method 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 →