get_stock_ledger
AI agents call get_stock_ledger 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.
Stock ledger retrieval is a query/fetch operation that accesses historical inventory transaction data. No description was provided, which slightly lowers confidence, but the naming pattern and context of sibling read tools (get_document, get_count) and the absence of write/delete indicators make this clearly a Read operation with minimal blast radius—it cannot modify or delete data, only retrieve it for analysis or…
From the tool's definition Tool name 'get_stock_ledger' follows read-operation naming convention. Server description indicates support for 'schema inspection' and tool siblings include 'get_document', 'get_count', 'find_items' which are clearly read operations.
Attacks that exploit this kind of access
get_stock_ledger. 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_stock_ledger: 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_stock_ledger 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_stock_ledger 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_stock_ledger. 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_stock_ledger 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 →