search_key_indicators
AI agents call search_key_indicators to retrieve information from Korean Stat without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or searches Korean statistical indicators from a public statistical API. It has no side effects, does not modify data, and does not execute code or trigger external operations. It belongs in the Read category with low severity since misuse would only involve accessing statistical data, a low-impact operation.
From the tool's definition Tool name 'search_key_indicators' and server description indicate data retrieval from KOSIS OpenAPI. Sibling tools like 'get_key_indicator', 'get_statistics_data', and 'browse_categories' are all read-only operations.
Attacks that exploit this kind of access
search_key_indicators. It is categorised as a Read tool in the Korean Stat MCP Server, which means it retrieves data without modifying state.
Register the Korean Stat MCP server in PolicyLayer and add a rule for search_key_indicators: 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 Korean Stat. Nothing to install.
search_key_indicators 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_key_indicators 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_key_indicators. 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_key_indicators is provided by the Korean Stat MCP server (seolcoding/korean-stat-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 →