get_crypto_prices
Get real-time cryptocurrency prices from Binance. Use this to check current crypto prices, 24-hour price changes, and market data for major cryptocurrencies. Supports common names (bitcoin, ethereum, solana) and direct ticker symbols. Parameters: symbol — Comma-separated cryptocurrency names or t...
This record as markdown: /tools/com-gadgethumans-swarm-x402-middleware/get-crypto-prices.md
What get_crypto_prices does on X402 Middleware
AI agents call get_crypto_prices to retrieve information from X402 Middleware 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 |
|---|---|---|---|
symbol | string | — |
Parameters from the server's own tool schema.
Why get_crypto_prices is rated Low
This tool retrieves market data from Binance without modifying, executing operations, or committing financial transactions. It is purely a data retrieval operation similar to a price lookup. While it is hosted on a payment middleware server (X402), the tool itself only performs read operations.
From the tool's definition Tool description states 'Get real-time cryptocurrency prices' and 'check current crypto prices, 24-hour price changes, and market data'. The parameters accept symbol names for querying.
Attacks that exploit this kind of access
The rule that runs get_crypto_prices safely
PolicyLayer is an MCP gateway: it sits between your AI agents and X402 Middleware, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_crypto_prices, this is the rule to start with:
get_crypto_prices 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 X402 Middleware, apply this rule, and every get_crypto_prices call is checked against it from then on.
Questions about get_crypto_prices
Get real-time cryptocurrency prices from Binance. Use this to check current crypto prices, 24-hour price changes, and market data for major cryptocurrencies. Supports common names (bitcoin, ethereum, solana) and direct ticker symbols. Parameters: symbol — Comma-separated cryptocurrency names or tickers (default: "bitcoin,ethereum"). Examples: "bitcoin", "ethereum,solana", "BTC,ETH,SOL". It is categorised as a Read tool in the X402 Middleware MCP Server, which means it retrieves data without modifying state.
get_crypto_prices accepts 1 parameter: symbol. The full parameter table on this page comes from the server's own tool schema.
Register the X402 Middleware MCP server in PolicyLayer and add a rule for get_crypto_prices: 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 X402 Middleware. Nothing to install.
get_crypto_prices 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_crypto_prices 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_crypto_prices. 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_crypto_prices is provided by the X402 Middleware MCP server (@gadgethumans/x402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on X402 Middleware, and thousands of servers like it.
This server
Across the catalogue