AI agents call list_tx_reasons to retrieve information from Vanam Erp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a straightforward lookup/read operation that retrieves reference data (transaction reason codes) from the ERP system. It enables chatbots to populate dropdowns or validate user input before processing, but performs no writes, deletions, or state changes itself. The tool is purely informational for downstream transaction processing.
From the tool's definition Tool description states it '조회한다' (queries/retrieves) a list of reasons for inventory transactions. Returns 'id and name' of each reason with no arguments required. No modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
재고 출고/불출 시 사용하는 사유 목록을 조회한다. 인자가 필요 없다. 사용자가 출고/불출 사유를 말하면 이 목록에서 맞는 사유의 id를 찾아라(처리에는 사유 이름이 아니라 사유 id가 필요하다). 각 사유의 id와 name을 반환한다. It is categorised as a Read tool in the Vanam Erp MCP Server, which means it retrieves data without modifying state.
Register the Vanam Erp MCP server in PolicyLayer and add a rule for list_tx_reasons: 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 Vanam Erp. Nothing to install.
list_tx_reasons 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 list_tx_reasons 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 list_tx_reasons. 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.
list_tx_reasons is provided by the Vanam Erp MCP server (leejunheon/vanam-erp-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 →