Multi-timeframe On-Balance Volume analysis. Detects accumulation/distribution through OBV trends and price/OBV divergences. Essential for confirming pump/dump signals - catches hidden accumulation (like BTR) or distribution masquerading as pumps. Returns OBV values, trends, and divergence alerts ...
AI agents call obv_analysis 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 is a technical analysis tool that retrieves and analyzes market data (price and volume) to generate trading signals and insights. It reads historical market data and produces analytical output without side effects. While it operates in a financial trading context, the tool itself only reads and analyzes data—it does not move money, execute trades, or commit financial obligations.
From the tool's definition Tool performs 'On-Balance Volume analysis' and 'Detects accumulation/distribution through OBV trends' - purely analytical operations that 'Returns OBV values, trends, and divergence alerts'.
Attacks that exploit this kind of access
Multi-timeframe On-Balance Volume analysis. Detects accumulation/distribution through OBV trends and price/OBV divergences. Essential for confirming pump/dump signals - catches hidden accumulation (like BTR) or distribution masquerading as pumps. Returns OBV values, trends, and divergence alerts across 5m, 15m, 1h, 4h timeframes. 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 obv_analysis: 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.
obv_analysis 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 obv_analysis 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 obv_analysis. 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.
obv_analysis 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 →