판매 입력. 실제 판매(출고) 전표를 ECOUNT에 등록합니다.
AI agents use ecount_create_sale to create or update resources in ECOUNT MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ECOUNT MCP Server environment.
This tool creates/registers sales documents (출고 전표 = shipment vouchers) in an ERP system. It modifies business data reversibly by recording sales transactions. While it has financial implications, the primary action is data creation/modification rather than moving money directly.
From the tool's definition Tool name 'ecount_create_sale' and description '판매 입력. 실제 판매(출고) 전표를 ECOUNT에 등록합니다.' (Create sale. Registers an actual sales (shipment) document in ECOUNT.)
Attacks that exploit this kind of access
판매 입력. 실제 판매(출고) 전표를 ECOUNT에 등록합니다. It is categorised as a Write tool in the ECOUNT MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ECOUNT MCP Server MCP server in PolicyLayer and add a rule for ecount_create_sale: 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_create_sale is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the ecount_create_sale 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_create_sale. 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_create_sale 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 →