Detect the current BTC market regime (bullish/bearish/neutral) using EMA crossovers and RSI momentum from Binance data. Returns regime with confidence score, suggested direction, panic detection, and reasoning. Use this to align your trades with macro conditions - trading against the regime signi...
AI agents call get_market_regime to retrieve information from Asterdex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs market analysis and detection without side effects. It queries existing market data, applies technical analysis calculations, and returns results to inform trading decisions. The tool itself does not execute trades, modify accounts, or commit financial resources—it is purely informational.
From the tool's definition Tool retrieves and analyzes market data ('Detect the current BTC market regime', 'Returns regime with confidence score') to provide informational output. Uses read-only analysis of Binance data via technical indicators (EMA, RSI).
Attacks that exploit this kind of access
Detect the current BTC market regime (bullish/bearish/neutral) using EMA crossovers and RSI momentum from Binance data. Returns regime with confidence score, suggested direction, panic detection, and reasoning. Use this to align your trades with macro conditions - trading against the regime significantly reduces edge. It is categorised as a Read tool in the Asterdex MCP Server, which means it retrieves data without modifying state.
Register the Asterdex MCP server in PolicyLayer and add a rule for get_market_regime: 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 Asterdex. Nothing to install.
get_market_regime 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_market_regime 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_market_regime. 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_market_regime is provided by the Asterdex MCP server (tyranosurasmax/asterdex-mcp-server). 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 →