ecount_create_job_order · ECOUNT MCP Server MCP

WHAT IT DOES

What ecount_create_job_order does on ECOUNT MCP Server

AI agents use ecount_create_job_order 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.

WHY IT NEEDS A POLICY

Why ecount_create_job_order needs a policy

This tool creates a new job order and registers a production plan in the ECOUNT ERP system. While reversible (orders can typically be cancelled or modified), it creates binding operational data that affects manufacturing workflows, inventory allocation, and production scheduling. The high severity reflects the business impact of incorrectly created job orders affecting supply chain operations.

From the tool's definition Tool name contains 'create_job_order' and description states '작업지시서 입력. 생산 계획을 ECOUNT에 등록합니다.' (Job order input. Registers production plan in ECOUNT). The 'create' and '등록' (register) verbs indicate data creation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ecount_create_job_order Rate-limited

ecount_create_job_order stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ecount_create_job_order": {
      "limits": [
        {
          "counter": "ecount_create_job_order_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ECOUNT MCP Server, so you can run agents against it safely.

FAQ

Questions about ecount_create_job_order

What does the ecount_create_job_order tool do? +

작업지시서 입력. 생산 계획을 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.

How do I enforce a policy on ecount_create_job_order? +

Register the ECOUNT MCP Server MCP server in PolicyLayer and add a rule for ecount_create_job_order: 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.

What risk level is ecount_create_job_order? +

ecount_create_job_order is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit ecount_create_job_order? +

Yes. Add a rate_limit block to the ecount_create_job_order 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.

How do I block ecount_create_job_order completely? +

Set action: deny in the PolicyLayer policy for ecount_create_job_order. 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.

What MCP server provides ecount_create_job_order? +

ecount_create_job_order 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.