Prediction market + derivatives data via Predexon aggregator. Tier 1 = $0.001/call, Tier 2 = $0.005/call. CANONICAL CROSS-VENUE (Tier 1) \u2014 Predexon v2 unified data layer: - markets \u2014 list canonical market/question containers with cross-venue Predexon IDs - markets/listings \u2014 venue-...
Part of the Blockrun server.
Free to start. No card required.
AI agents call blockrun_markets to retrieve information from Blockrun 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 blockrun_markets 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": {
"blockrun_markets": {}
}
}See the full Blockrun policy for all 16 tools.
These attack patterns abuse exactly the kind of access blockrun_markets 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.
Prediction market + derivatives data via Predexon aggregator. Tier 1 = $0.001/call, Tier 2 = $0.005/call. CANONICAL CROSS-VENUE (Tier 1) \u2014 Predexon v2 unified data layer: - markets \u2014 list canonical market/question containers with cross-venue Predexon IDs - markets/listings \u2014 venue-native executable listings flattened across canonical markets - outcomes/:predexon_id \u2014 resolve a canonical outcome ID to its market context + venue listings Filter with ?venue=polymarket|kalshi|limitless|opinion|predictfun, ?status=, ?category=, ?league=, ?event_id=, ?pagination_key= POLYMARKET (Tier 1): - polymarket/events, polymarket/markets \u2014 list events/markets (filter, sort, paginate) - polymarket/markets/keyset, polymarket/events/keyset \u2014 same data, cursor-based keyset pagination (use ?pagination_key=) - polymarket/crypto-updown \u2014 crypto up/down markets - polymarket/market-price/:token_id \u2014 current/historical price - polymarket/candlesticks/:condition_id \u2014 OHLCV by market - polymarket/candlesticks/token/:token_id \u2014 OHLCV by single outcome token - polymarket/volume-chart/:condition_id \u2014 volume w/ YES/NO split - polymarket/orderbooks, polymarket/trades, polymarket/activity - polymarket/markets/:token_id/volume, polymarket/markets/:condition_id/open_interest - polymarket/positions \u2014 user positions - polymarket/leaderboard, polymarket/leaderboard/market/:condition_id - polymarket/cohorts/stats, polymarket/market/:condition_id/top-holders - polymarket/uma/markets, polymarket/uma/market/:condition_id \u2014 UMA oracle questions/timeline POLYMARKET (Tier 2 \u2014 wallet/smart-money analytics): - polymarket/wallet/:wallet \u2014 full smart-wallet profile - polymarket/wallet/:wallet/markets, .../similar - polymarket/wallet/pnl/:wallet, .../positions/:wallet, .../volume-chart/:wallet - polymarket/wallets/profiles, polymarket/wallets/filter \u2014 batch + AND/OR filter - polymarket/market/:condition_id/smart-money, polymarket/markets/smart-activity WALLET IDENTITY & CLUSTERING (Tier 2) \u2014 cross-context labels + on-chain relationship graph: - polymarket/wallet/identity/:wallet \u2014 fetch identity + profile metadata for one wallet - polymarket/wallet/identities \u2014 POST { addresses: [...] } for bulk lookup (up to 200 wallets) - polymarket/wallet/:address/cluster \u2014 discover wallets connected via on-chain transfers + identity proofs SPORTS (Tier 1): - sports/categories \u2014 list available sports categories - sports/markets \u2014 list sports markets grouped by game (filter ?league=, ?sport_type=, ?status=, ?venue=) - sports/markets/:game_id \u2014 single sports game with all venue outcomes - sports/outcomes/:predexon_id \u2014 equivalent sports outcomes across venues for a Predexon ID KALSHI (Tier 1): kalshi/markets, kalshi/trades, kalshi/orderbooks LIMITLESS / OPINION / PREDICT.FUN (Tier 1): {platform}/markets, {platform}/orderbooks DFLOW: dflow/trades (T1), dflow/wallet/positions/:wallet (T2), dflow/wallet/pnl/:wallet (T2) BINANCE FUTURES (Tier 2): binance/candles/:symbol, binance/ticks/:symbol CROSS-PLATFORM: - matching-markets, matching-markets/pairs \u2014 equivalent markets across Polymarket+Kalshi (T2) - markets/search \u2014 search across all platforms in one call (T2) Pass query params via. It is categorised as a Read tool in the Blockrun MCP Server, which means it retrieves data without modifying state.
Register the Blockrun MCP server in PolicyLayer and add a rule for blockrun_markets: 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 Blockrun. Nothing to install.
blockrun_markets 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 blockrun_markets 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 blockrun_markets. 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.
blockrun_markets is provided by the Blockrun MCP server (@blockrun/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Blockrun 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.