Monitor stablecoin health: peg deviation from $1.00, supply changes (minting/burning), market cap, backing composition, and depeg risk score. Use this tool when: - A DeFi agent needs to verify a stablecoin is holding its peg before using it in a protocol - You want to detect early warning signs o...
AI agents call get_stablecoins to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that queries blockchain/market state without side effects. While the server operates on USDC and involves financial data, this specific tool only reads stablecoin health metrics and does not move money, execute trades, or trigger transactions. It enables informed decision-making but does not itself commit financial obligations or actions.
From the tool's definition Tool retrieves and monitors stablecoin metrics: 'peg deviation from $1.00, supply changes (minting/burning), market cap, backing composition, and depeg risk score' with return data being 'symbol, current_price, peg_deviation_pct, market_cap_usd, 24h_supply_c'.
Attacks that exploit this kind of access
Monitor stablecoin health: peg deviation from $1.00, supply changes (minting/burning), market cap, backing composition, and depeg risk score. Use this tool when: - A DeFi agent needs to verify a stablecoin is holding its peg before using it in a protocol - You want to detect early warning signs of a stablecoin collapse (e.g. UST-style depeg) - A risk agent is assessing counterparty risk in stablecoin-denominated positions - An agent is comparing stablecoin options for yield farming and needs health data Returns per token: symbol, current_price, peg_deviation_pct, market_cap_usd, 24h_supply_change_pct, backing_type (FIAT/CRYPTO/ALGORITHMIC), depeg_risk_score (0-100, 100=imminent), audit_status. Example: getStablecoins({ tokens:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_stablecoins: 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 Omni Service Node. Nothing to install.
get_stablecoins 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_stablecoins 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_stablecoins. 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_stablecoins is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →