// SCAN REPORT

Tradeblocks

69 tools. 16 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 27 Jun 2026

16 can modify or destroy data

53 read-only

69 tools total

Community server · catalogue entry verified 27/06/2026

How to control Tradeblocks ↓

TOOL MAP

What Tradeblocks exposes to your agents

Read (53) Write / Execute (13) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Tradeblocks tools

Destructive · Critical purge_market_table Delete all data from a market table and clear its sync metadata. Use when market data is corrupted and needs to be re-imported. After purgin Destructive · High delete_profile Delete a strategy profile by block_id and strategy_name. Idempotent: deleting a nonexistent profile returns success with a not-found message Destructive · High unregister_underlying Remove a user or user-override ticker entry. Bundled defaults cannot be removed; removing a user-override reverts the entry back to its bund Execute · High batch_exit_analysis Analyze how a candidate exit policy would perform across multiple trades in a block. Replays each matching trade, evaluates exit triggers ag

16 of Tradeblocks's 69 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Tradeblocks

PolicyLayer is an MCP gateway — it sits between your AI agents and Tradeblocks, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_profile": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "compute_vix_context": {
    "limits": [
      {
        "counter": "compute_vix_context_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "analyze_discrepancies": {
    "limits": [
      {
        "counter": "analyze_discrepancies_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Tradeblocks — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON TRADEBLOCKS →

Instant setup, no code required.

FULL CATALOGUE

All 69 Tradeblocks tools

DESTRUCTIVE 3 tools

Destructive delete_profile Delete a strategy profile by block_id and strategy_name. Idempotent: deleting a nonexistent profile returns su Destructive purge_market_table Delete all data from a market table and clear its sync metadata. Use when market data is corrupted and needs t Destructive unregister_underlying Remove a user or user-override ticker entry. Bundled defaults cannot be removed; removing a user-override reve

EXECUTE 5 tools

Execute batch_exit_analysis Analyze how a candidate exit policy would perform across multiple trades in a block. Replays each matching tra Execute portfolio_structure_map Build a Vol_Regime x Trend_Direction matrix (18 cells) across all profiled strategies. Shows per-strategy stat Execute run_monte_carlo Run Monte Carlo simulation to project future performance and calculate risk metrics Execute run_sql Execute a SQL query against the DuckDB analytics database. SELECT runs freely. All mutating operations (DELETE Execute run_walk_forward Execute walk-forward analysis to test parameter robustness across time windows

WRITE 8 tools

Write compute_vix_context Compute cross-ticker VIX context enrichment (Vol_Regime, Term_Structure_State, VIX ratios, etc.) for a date ra Write import_csv Import a CSV file from the local filesystem into the blocks directory. Creates a new block that can be analyze Write import_flat_file Provider-agnostic flat-file ingest. Reads rows from a local file (parquet, csv, jsonl, .gz \u2014 anything Duc Write import_from_database Import minute bars from an external DuckDB database into the spot dataset via SpotStore.writeBars. The externa Write import_market_csv Import minute bars from a CSV file into the spot dataset via SpotStore.writeBars. Daily / date_context outputs Write profile_strategy Create or update a strategy profile for a block. Stores structure type, greeks bias, legs, entry filters, exit Write register_underlying Add or update an underlying\u2192roots mapping in the ticker registry. Persists to {dataRoot}/market/underlyin Write resolve_root Debug helper: show how a symbol resolves through the ticker registry. Accepts bare roots (

READ 53 tools

Read analyze_discrepancies Analyze slippage patterns between backtest and actual trades. Detects systematic biases (direction, time-of-da Read analyze_edge_decay Run comprehensive edge decay analysis combining all 5 signal categories: period metrics, rolling metrics, Mont Read analyze_exit_triggers Analyze when exit triggers would fire on a trade replay. Runs replay internally -- provide block_id + trade_in Read analyze_live_alignment Compare backtest trades against actual (reporting log) trades to assess live execution alignment. Computes dir Read analyze_period_metrics Segment a block Read analyze_regime_comparison Run dual Monte Carlo simulations comparing full trade history vs recent window to detect regime divergence. Co Read analyze_regime_performance Break down a block Read analyze_rolling_metrics Compute rolling window statistics, quarterly seasonal averages, and recent-vs-historical comparison with struc Read analyze_slippage_trends Analyze slippage trends over time with statistical significance testing. Detects improvement/degradation patte Read analyze_structure_fit Analyze how well a strategy fits various market dimensions using its stored profile. Returns performance break Read analyze_walk_forward_degradation Run progressive walk-forward analysis to track whether out-of-sample performance is degrading relative to in-s Read block_diff Compare two blocks with strategy overlap analysis and P/L attribution. Shows which strategies are shared vs un Read calculate_orb Calculate Opening Range Breakout (ORB) levels from market.spot bar data. ORB range defined by high/low (or clo Read compare_backtest_to_actual Compare backtest (tradelog.csv) results to actual reported trades (reportinglog.csv) with scaling options for Read compare_blocks Compare performance statistics across multiple portfolios side-by-side. Use blockIds from list_blocks. Read decompose_greeks Decompose a trade Read describe_database Get complete database schema: all tables, columns, types, row counts, and example queries. Call this BEFORE us Read drawdown_attribution Identify which strategies contributed most to losses during the portfolio Read enrich_market_data Compute technical indicator fields from raw OHLCV data in market.spot_daily and write derived fields to market Read enrich_trades Enrich trades with market context from market.enriched + market.spot_daily (ticker-specific + VIX tickers) and Read fetch_bars Fetch OHLCV bars for one or more tickers over a date range. Uses the active market data provider (env MARKET_D Read fetch_chain Fetch the historical option contract list for one or more underlyings over a date range. Writes contract metad Read fetch_quotes Fetch minute-level option quotes. Two modes \u2014 pass EITHER Read filter_curve Sweep filter thresholds for a field and show performance at each threshold. Use after find_predictive_fields t Read find_predictive_fields Identify which trade entry conditions predict profitability by calculating Pearson correlations between all nu Read get_backtest_help Get Option Omega backtesting guidance. Covers strategy setup, strike selection, entry/exit conditions, risk co Read get_block_info Get detailed metadata for a block including available strategies, date range, and daily log status. Use blockI Read get_correlation_matrix Calculate correlation matrix between strategies to identify diversification Read get_field_statistics Get detailed statistics for a specific field including min/max/avg/median/stdDev, percentiles, and histogram Read get_greeks_attribution Decompose a block Read get_option_snapshot Fetch live option chain snapshot with greeks, IV, open interest, and quotes from Massive.com. Returns current Read get_performance_charts Get chart data for performance visualizations: equity curves, drawdowns, return distributions, rolling metrics Read get_period_returns Get P&L breakdown by period (monthly, weekly, or daily) with gross P/L, commissions, and net P/L Read get_position_sizing Calculate Kelly criterion position sizing for optimal capital allocation Read get_reporting_log_stats Get detailed statistics about actual trade execution from reporting log. Returns per-strategy breakdown with t Read get_statistics Get comprehensive portfolio statistics: win rate, Sharpe ratio, max drawdown, P&L metrics, and more. Use block Read get_strategy_comparison Compare all strategies within a block with optional filtering and sorting Read get_strategy_profile Retrieve a single strategy profile by block_id and strategy_name. Returns the full profile including all schem Read get_tail_risk Calculate Gaussian copula tail dependence to identify extreme co-movement risk Read list_blocks START HERE: List all available portfolio blocks. Returns blockId values needed for all other tools (get_statis Read list_profiles List strategy profiles. Provide block_id to filter by block, or omit to list all profiles across all blocks. R Read list_underlyings List all ticker registry entries (bundled defaults + user-added + user-overrides). Each entry is annotated wit Read marginal_contribution Calculate how each strategy affects portfolio risk-adjusted returns (Sharpe/Sortino). Shows marginal contribut Read portfolio_health_check Run comprehensive portfolio health assessment combining correlation, tail risk, Monte Carlo, walk-forward anal Read refresh_market_data Composite daily-refresh driver. Calls fetch_bars \u2192 fetch_chain \u2192 fetch_quotes \u2192 compute_vix_con Read regime_allocation_advisor Cross-reference strategy profiles Read replay_trade Replay a trade using historical minute-level option bars. Reads option-leg quotes via QuoteStore and underlyin Read strategy_similarity Detect potentially redundant strategies based on correlation, tail dependence, and trading day overlap. Flags Read stress_test Analyze portfolio performance during historical market stress scenarios (COVID crash, 2022 bear, VIX spikes, e Read suggest_filters Analyze a block Read suggest_strategy_matches Suggest matches between backtest and actual strategies based on P/L correlation when names don Read validate_entry_filters Validate effectiveness of a strategy Read what_if_scaling Explore strategy weight combinations within a portfolio. Answer

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Tradeblocks

Can an AI agent delete data through the Tradeblocks MCP server? +

Yes. The Tradeblocks server exposes 3 destructive tools including delete_profile, purge_market_table, unregister_underlying. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Tradeblocks? +

The Tradeblocks server has 8 write tools including compute_vix_context, import_csv, import_flat_file. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Tradeblocks.

How many tools does the Tradeblocks MCP server expose? +

69 tools across 4 categories: Destructive, Execute, Read, Write. 53 are read-only. 16 can modify, create, or delete data.

How do I enforce a policy on Tradeblocks? +

Register the Tradeblocks MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Tradeblocks tool call.

Deterministic rules across all 69 Tradeblocks tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON TRADEBLOCKS →

Instant setup, no code required.

69 Tradeblocks tools catalogued and risk-classified — across an index of 43,000+ MCP servers.