get_item_price
AI agents call get_item_price 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.
This tool retrieves pricing data from an ERPNext instance. Despite the empty description, the naming pattern and context of sibling tools (get_*, find_*) strongly suggest a read-only query operation with no side effects. The confidence is reduced slightly (0.85 instead of 0.95+) due to the missing description, but the evidence from the tool name and established patterns on this server is clear.
From the tool's definition Tool name 'get_item_price' indicates a query/retrieval operation consistent with sibling tools like 'get_document', 'get_customer_details', and 'get_count' which are all Read operations.
Attacks that exploit this kind of access
get_item_price. 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_item_price: 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_item_price 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_item_price 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_item_price. 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_item_price 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.
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 →