매출·매입전표 II 자동분개. 회계 전표(세금계산서)를 ECOUNT에 등록합니다.
AI agents use ecount_create_invoice 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 and registers financial accounting records (invoices and journal entries) in an ERP system. While it modifies data reversibly (invoices can be edited or cancelled in most ERP systems), it creates binding accounting records that affect financial statements and tax compliance.
From the tool's definition Tool name 'ecount_create_invoice' and description indicate creation of accounting vouchers (tax invoices/세금계산서) and automatic journal entries (자동분개) in ECOUNT ERP. The Korean description translates to 'Sales/Purchase voucher II automatic journal entry.
Attacks that exploit this kind of access
매출·매입전표 II 자동분개. 회계 전표(세금계산서)를 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_invoice: 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_invoice 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_invoice 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_invoice. 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_invoice 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 →