로컬 종목 마스터 DB의 시장별 종목 수와 마지막 갱신일을 조회합니다.
AI agents call kis_master_status 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.
This tool retrieves metadata about a local database (market count and last update timestamp). It has no side effects, does not modify data, does not execute trades, and does not commit financial obligations. It is a pure information retrieval operation, consistent with Read category tools like 'get' or 'list'. The blast radius is minimal since the output is static metadata only.
From the tool's definition Tool name: kis_master_status. Description translates to: 'Queries the number of securities by market and last update date in the local ticker master DB.' Keywords: 조회 (query/check), 수 (count), 갱신일 (update date) — all read operations.
Attacks that exploit this kind of access
로컬 종목 마스터 DB의 시장별 종목 수와 마지막 갱신일을 조회합니다. 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 kis_master_status: 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.
kis_master_status 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 kis_master_status 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 kis_master_status. 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.
kis_master_status is provided by the KIS MCP Server MCP server (nangchang/stock-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 →