재고현황 단건 조회. 특정 품목의 특정 일자 기준 재고 수량을 조회합니다.
AI agents call ecount_get_inventory to retrieve information from ECOUNT 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 inventory quantity data for a specific product on a specific date. It performs a read-only query operation with no side effects—it does not create, modify, delete, or execute any transactions. The action is a simple data retrieval from the ERP system's inventory module.
From the tool's definition Tool name contains 'get_inventory' and description states '재고현황 단건 조회' (single inventory status inquiry) and '재고 수량을 조회합니다' (queries/retrieves inventory quantity). The verb '조회' means 'to query/retrieve' without modification.
Attacks that exploit this kind of access
재고현황 단건 조회. 특정 품목의 특정 일자 기준 재고 수량을 조회합니다. It is categorised as a Read tool in the ECOUNT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ECOUNT MCP Server MCP server in PolicyLayer and add a rule for ecount_get_inventory: 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 ECOUNT MCP Server. Nothing to install.
ecount_get_inventory 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 ecount_get_inventory 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 ecount_get_inventory. 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.
ecount_get_inventory is provided by the ECOUNT MCP Server MCP server (storehausai/mcp-server-ecount). 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 →