Comprehensive analysis combining VPVR, orderbook depth at key levels, trading session context, and BTC correlation. Use this for high-conviction trade decisions. Returns everything needed to assess a short/long setup.
AI agents call deep_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 tool retrieves and analyzes market data (volume profile, orderbook depth, session context, correlation metrics) to support decision-making. It has no side effects, does not execute orders, does not modify data, and does not move money. Despite being used in a trading platform context, the tool itself only reads and processes existing market information.
From the tool's definition Tool name 'deep_analysis' and description states it performs 'analysis combining VPVR, orderbook depth, trading session context, and BTC correlation' and 'returns everything needed to assess' — purely informational retrieval with no execution, creation,…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Comprehensive analysis combining VPVR, orderbook depth at key levels, trading session context, and BTC correlation. Use this for high-conviction trade decisions. Returns everything needed to assess a short/long setup. 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 deep_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.
deep_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 deep_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 deep_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.
deep_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 →