Calculate the Since Change for a given trading pair using Binance OHLCV data
AI agents call calculate_since_change to retrieve information from Crypto Indicators without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and calculates a technical indicator ('Since Change') based on historical OHLCV (Open, High, Low, Close, Volume) data from Binance. It is a read/query operation with no side effects — it fetches market data and performs a calculation, consistent with all sibling tools on this server which are calculation/analysis tools.
From the tool's definition Calculate the Since Change for a given trading pair using Binance OHLCV data
Documented attack patterns abuse exactly the kind of access calculate_since_change gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crypto Indicators, and nothing reaches the server without passing your rules. This is the rule we recommend for calculate_since_change:
{
"version": "1",
"default": "deny",
"tools": {
"calculate_since_change": {}
}
}calculate_since_change is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Calculate the Since Change for a given trading pair using Binance OHLCV data. It is categorised as a Read tool in the Crypto Indicators MCP Server, which means it retrieves data without modifying state.
Register the Crypto Indicators MCP server in PolicyLayer and add a rule for calculate_since_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 Indicators. Nothing to install.
calculate_since_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 calculate_since_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 calculate_since_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.
calculate_since_change is provided by the Crypto Indicators MCP server (kukapay/crypto-indicators-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Crypto Indicators, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
78 Crypto Indicators tools catalogued and risk-classified — across an index of 43,000+ MCP servers.