AI agents call crypto.kimchi-premium to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns cryptocurrency price premium data between Korean and global exchanges. It performs a read-only retrieval and calculation operation without side effects. While it exists within a financial context (crypto prices), the tool itself does not move money, execute trades, or commit financial obligations—it only fetches and compares price information. This is a standard data retrieval use case.
From the tool's definition Tool description indicates it 'Upbit KRW price vs global USD price' — a retrieval and comparison of publicly available market data. No creation, modification, deletion, code execution, or financial transaction occurs.
Attacks that exploit this kind of access
Korean-exchange crypto premium: Upbit KRW price vs global USD price (x USD/KRW), as a %. Pass symbol(s). It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for crypto.kimchi-premium: 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 Mcp. Nothing to install.
crypto.kimchi-premium 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 crypto.kimchi-premium 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 crypto.kimchi-premium. 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.
crypto.kimchi-premium is provided by the MCP server (@2sio/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 →