AI agents call krx_rate_limit to retrieve information from Krx Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves usage statistics about API quota consumption. It has no side effects, does not modify data, execute commands, or commit financial transactions. It is a straightforward monitoring/inspection function analogous to a 'get' or 'status' query. The low severity reflects minimal blast radius: misuse would only waste an API call or reveal quota information, neither of which causes harm.
From the tool's definition Tool name and description indicate it 'Check[s] daily API call usage' and 'monitor[s] remaining quota' — purely informational queries with no modification or execution of external operations.
Attacks that exploit this kind of access
Check daily API call usage. KRX API has a 10,000 calls/day limit. Use this to monitor remaining quota before making bulk queries. It is categorised as a Read tool in the Krx Cli MCP Server, which means it retrieves data without modifying state.
Register the Krx Cli MCP server in PolicyLayer and add a rule for krx_rate_limit: 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 Krx Cli. Nothing to install.
krx_rate_limit 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 krx_rate_limit 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 krx_rate_limit. 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.
krx_rate_limit is provided by the Krx Cli MCP server (kyo504/krx-cli). 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 →