ECOUNT ERP 연결 테스트. API 인증 정보(회사코드, 사용자ID, API키)가 올바른지 확인하고,
AI agents call ecount_test_connection 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 is a diagnostic/validation tool that only queries and confirms the state of API authentication. It retrieves or verifies information without modifying any data in the ERP system. Misuse would have minimal impact—a failed test connection attempt causes no irreversible harm or state change to the system.
From the tool's definition Tool name 'ecount_test_connection' and description indicating it tests/verifies API authentication credentials ('API 인증 정보가 올바른지 확인하고'). The tool performs a connection test and validation check with no data modification, creation, or side effects.
Attacks that exploit this kind of access
ECOUNT ERP 연결 테스트. API 인증 정보(회사코드, 사용자ID, API키)가 올바른지 확인하고,. 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_test_connection: 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_test_connection 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_test_connection 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_test_connection. 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_test_connection 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 →