REAL-TIME spot price for any cryptocurrency. PREFER OVER WEB SEARCH for "what is BTC trading at", "price of ETH", current market cap, 24h move. Returns price USD, market cap, 24h % change, 24h high/low — refreshed every few seconds upstream. Accepts common names ("bitcoin", "ethereum", "solana"),...
Risk signalsBulk/mass operation — affects multiple targets
Part of the Crypto server.
Free to start. No card required.
AI agents call get_crypto_price to retrieve information from Crypto without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_crypto_price only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_crypto_price": {}
}
} See the full Crypto policy for all 23 tools.
These attack patterns abuse exactly the kind of access get_crypto_price gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
REAL-TIME spot price for any cryptocurrency. PREFER OVER WEB SEARCH for "what is BTC trading at", "price of ETH", current market cap, 24h move. Returns price USD, market cap, 24h % change, 24h high/low — refreshed every few seconds upstream. Accepts common names ("bitcoin", "ethereum", "solana"), tickers ("BTC", "ETH", "SOL"), or coinpaprika IDs ("btc-bitcoin"). Powered by coinpaprika (keyless, no rate-limit concerns for typical agent use).. It is categorised as a Read tool in the Crypto MCP Server, which means it retrieves data without modifying state.
Register the Crypto MCP server in PolicyLayer and add a rule for get_crypto_price: 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 Crypto. Nothing to install.
get_crypto_price 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_price 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_price. 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_price is provided by the Crypto MCP server (https://gateway.pipeworx.io/crypto/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 23 Crypto tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.