check_stablecoin_peg
utilpeek: Check stablecoin peg: is USDC, USDT, DAI, USDe or PYUSD holding its dollar peg. For supply by chain use get_stablecoin_supply. Returns whether USDC, USDT, DAI, USDe or PYUSD holds its dollar peg, from Ethereum Uniswap V3 pools: price_usd, deviation_bps, on_peg / watch / off_peg status (...
This record as markdown: /tools/dev-tanod-tanod/check-stablecoin-peg.md
What check_stablecoin_peg does on Tanod
AI agents call check_stablecoin_peg 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
coins | object | — | Stablecoins to check, any of USDC, USDT, DAI, USDe and PYUSD (case does not matter). Omit for all five; an unknown coin is a 422 that lists the supported ones. |
Parameters from the server's own tool schema.
Why check_stablecoin_peg is rated Low
Even though check_stablecoin_peg 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.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs check_stablecoin_peg safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Tanod, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_stablecoin_peg, this is the rule to start with:
check_stablecoin_peg is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Tanod, apply this rule, and every check_stablecoin_peg call is checked against it from then on.
Questions about check_stablecoin_peg
utilpeek: Check stablecoin peg: is USDC, USDT, DAI, USDe or PYUSD holding its dollar peg. For supply by chain use get_stablecoin_supply. Returns whether USDC, USDT, DAI, USDe or PYUSD holds its dollar peg, from Ethereum Uniswap V3 pools: price_usd, deviation_bps, on_peg / watch / off_peg status (50 and 200 bps), the pools and their depth, and the read time. Indicative on-chain prices, not an oracle; non-USDC coins are priced in USDC and USDC by cross-check; pools read at most every 30 s; a failed coin is in errors; all coins failing is a 502 and an unknown coin a 422 (neither charged). Typically 1 to 4 s (one chain read), under 100 ms when cached. Price: USD 0.001. Free: 10 utilpeek calls per IP per UTC day. Docs: https://tanod.dev/learn/stablecoin-peg-check-api.html. It is categorised as a Read tool in the Tanod MCP Server, which means it retrieves data without modifying state.
check_stablecoin_peg accepts 1 parameter: coins. The full parameter table on this page comes from the server's own tool schema.
Register the Tanod MCP server in PolicyLayer and add a rule for check_stablecoin_peg: 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.
check_stablecoin_peg 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 check_stablecoin_peg 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 check_stablecoin_peg. 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.
check_stablecoin_peg 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.
This server
Across the catalogue