Get 24-hour price statistics for a cryptocurrency from Binance.
AI agents call get_price_change to retrieve information from Crypto HTTP MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves cryptocurrency price data from Binance's public API. It performs no write, modification, deletion, code execution, or financial transaction operations. While the broader server provides cryptocurrency data that could inform financial decisions, this specific tool is purely informational—it reads and returns market statistics.
From the tool's definition Tool name 'get_price_change' and description 'Get 24-hour price statistics for a cryptocurrency from Binance' indicate a data retrieval operation that fetches historical price statistics without modification.
Attacks that exploit this kind of access
Get 24-hour price statistics for a cryptocurrency from Binance. It is categorised as a Read tool in the Crypto HTTP MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Crypto HTTP MCP Server MCP server in PolicyLayer and add a rule for get_price_change: 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 HTTP MCP Server. Nothing to install.
get_price_change 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_price_change 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_price_change. 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_price_change is provided by the Crypto HTTP MCP Server MCP server (joheiss/docker-mcp). 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 →