Low Risk

evolution_fetch_market_data

Fetch OHLCV market data from Binance for evolution analysis. Downloads historical price bars for backtesting and pattern discovery. Use this before discover_patterns or run_backtest to get data. Args: symbol: Trading pair (e.g. "BTCUSDT", "ETHUSDT") timeframe: Bar timeframe — "5m", "15m...

Part of the Tradememory Protocol MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents call evolution_fetch_market_data to retrieve information from Tradememory Protocol 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 evolution_fetch_market_data 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.

mnemox-ai-tradememory-protocol.yaml
tools:
  evolution_fetch_market_data:
    rules:
      - action: allow

See the full Tradememory Protocol policy for all 15 tools.

Tool Name evolution_fetch_market_data
Category Read
Risk Level Low

View all 15 tools →

Agents calling read-class tools like evolution_fetch_market_data have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the evolution_fetch_market_data tool do? +

Fetch OHLCV market data from Binance for evolution analysis. Downloads historical price bars for backtesting and pattern discovery. Use this before discover_patterns or run_backtest to get data. Args: symbol: Trading pair (e.g. "BTCUSDT", "ETHUSDT") timeframe: Bar timeframe — "5m", "15m", "1h", "4h", "1d" days: Number of days of history to fetch (default 90). It is categorised as a Read tool in the Tradememory Protocol MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on evolution_fetch_market_data? +

Add a rule in your Intercept YAML policy under the tools section for evolution_fetch_market_data. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Tradememory Protocol MCP server.

What risk level is evolution_fetch_market_data? +

evolution_fetch_market_data is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit evolution_fetch_market_data? +

Yes. Add a rate_limit block to the evolution_fetch_market_data rule in your Intercept 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.

How do I block evolution_fetch_market_data completely? +

Set action: deny in the Intercept policy for evolution_fetch_market_data. 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.

What MCP server provides evolution_fetch_market_data? +

evolution_fetch_market_data is provided by the Tradememory Protocol MCP server (mnemox-ai/tradememory-protocol). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Tradememory Protocol

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.