search_elw_api
AI agents call search_elw_api to retrieve information from KIS MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
ELW searches retrieve market data without modifying or executing trades. However, confidence is lowered due to empty description. Severity is medium because the broader server facilitates financial trading—misuse of market data access could support malicious trading strategies, but the tool itself only reads. In a financial trading context, even Read operations warrant elevated severity.
From the tool's definition Tool name 'search_elw_api' indicates data retrieval of ELW (Equity-Linked Warrant) information. No description provided, but 'search' and 'get' patterns are typical Read operations. The server context shows this is part of a KIS trading platform API suite.
Attacks that exploit this kind of access
search_elw_api. It is categorised as a Read tool in the KIS MCP Server MCP Server, which means it retrieves data without modifying state.
Register the KIS MCP Server MCP server in PolicyLayer and add a rule for search_elw_api: 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 KIS MCP Server. Nothing to install.
search_elw_api 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 search_elw_api 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 search_elw_api. 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.
search_elw_api is provided by the KIS MCP Server MCP server (soyjefu/kis-mcp). 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 →