New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_local_crypto_premiums

utilpeek: Use when an agent needs to gauge local demand for crypto: the kimchi or USDT premium on local exchanges vs the global price. For global sentiment use get_crypto_fear_greed_index. Returns BTC, ETH and USDT on large local exchanges in KR, JP, ID, PH, TR, BR, MX and AR in USD, with each ve...

SERVERTanod SOURCEhttps://tanod.dev/mcp
Low RISK CLASS
Category Read
Parameters 20 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-tanod-tanod/get-local-crypto-premiums.md

What get_local_crypto_premiums does on Tanod

AI agents call get_local_crypto_premiums to retrieve information from Tanod without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
asset object — BTC, ETH or USDT (default: all three)
country object — ISO 3166-1 alpha-2: KR, JP, ID, PH, TR, BR, MX or AR (default: all)

Parameters from the server's own tool schema.

Why get_local_crypto_premiums is rated Low

Even though get_local_crypto_premiums only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about get_local_crypto_premiums

What does the get_local_crypto_premiums tool do? +

utilpeek: Use when an agent needs to gauge local demand for crypto: the kimchi or USDT premium on local exchanges vs the global price. For global sentiment use get_crypto_fear_greed_index. Returns BTC, ETH and USDT on large local exchanges in KR, JP, ID, PH, TR, BR, MX and AR in USD, with each venue's premium to the global price and the FX source and date. Input: optional asset and country; both default to all. Last trades from public tickers, cached 30 s; references are Chainlink (BTC, ETH) and 1.0 (USDT); FX is the ECB daily fixing (BCRA for ARS), so under about 0.5 % is noise. Venue terms are unclear and each is credited. A failed venue is listed in errors; nothing priced is a 503 (not charged). Informational only, not investment advice. Typically under 0.5 s from cache; up to about 10 s when the venues are fetched. Price: USD 0.002. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/kimchi-premium-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.

What parameters does get_local_crypto_premiums accept? +

get_local_crypto_premiums accepts 2 parameters: asset, country. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_local_crypto_premiums? +

Register the Tanod MCP server in PolicyLayer and add a rule for get_local_crypto_premiums: 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 Tanod. Nothing to install.

What risk level is get_local_crypto_premiums? +

get_local_crypto_premiums is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_local_crypto_premiums? +

Yes. Add a rate_limit block to the get_local_crypto_premiums 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.

How do I block get_local_crypto_premiums completely? +

Set action: deny in the PolicyLayer policy for get_local_crypto_premiums. 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.

What MCP server provides get_local_crypto_premiums? +

get_local_crypto_premiums is provided by the Tanod MCP server (https://tanod.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Tanod, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Tanod's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.