게시글 입력. ECOUNT ERP 게시판에 글을 등록합니다.
AI agents use ecount_create_board_post 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 new board posts within an ERP system. Creation of content is a Write operation by definition. It is not destructive since posts can be edited or deleted later. The severity is low because bulletin board posts typically do not directly impact critical business data, transactions, or financial records — they are informational/communication content.
From the tool's definition '게시글 입력' (board post input) and 'ECOUNT ERP 게시판에 글을 등록합니다' (registers posts to ECOUNT ERP bulletin board) — creates/adds content to a board that is reversible.
Attacks that exploit this kind of access
게시글 입력. ECOUNT ERP 게시판에 글을 등록합니다. 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_board_post: 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_board_post 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_board_post 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_board_post. 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_board_post 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 →