발주서 조회. 특정 기간의 발주서 목록을 조회합니다.
AI agents call ecount_get_purchase_orders 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 and lists purchase orders for a specific period. It performs a read-only query operation on existing data with no ability to create, modify, delete, or execute actions. The Korean description confirms it is a lookup/inquiry function (조회), not a write or execute operation.
From the tool's definition Tool name contains 'get' and description states '발주서 조회' (purchase order inquiry/query) and '목록을 조회합니다' (retrieves a list). These are retrieval operations with no side effects.
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_purchase_orders: 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_purchase_orders 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_purchase_orders 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_purchase_orders. 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_purchase_orders 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 →