get_key_indicator_details
AI agents call get_key_indicator_details 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 appears to retrieve detailed information about key indicators from the KOSIS OpenAPI. It performs a query/fetch operation with no side effects—it only retrieves and returns data without modifying, deleting, or executing external operations. The 'get_' prefix is a strong signal of a Read operation.
From the tool's definition Tool name 'get_key_indicator_details' and sibling tools 'get_key_indicator', 'get_statistics_data', 'get_table_metadata' all indicate retrieval operations. Server purpose is to 'search, retrieve, and analyze Korean statistical data'.
Attacks that exploit this kind of access
get_key_indicator_details. 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 get_key_indicator_details: 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.
get_key_indicator_details 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 get_key_indicator_details 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 get_key_indicator_details. 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.
get_key_indicator_details 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 →