Get historical price chart data for a crypto token — timestamped prices for trend analysis. WHEN TO USE: For crypto price history and charting. Use veroq_crypto for current snapshot, this for historical trend. RETURNS: Sampled price history with timestamp, price, volume, and market cap per data p...
AI agents call veroq_crypto_chart to retrieve information from Veroq without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns historical financial data for analysis purposes only. It has no side effects, cannot modify state, execute operations, or affect financial transactions. The returned data is informational only, suitable for charting and trend analysis. Low severity because misuse would only affect the agent's analysis accuracy, not cause external harm or financial impact.
From the tool's definition Tool retrieves 'historical price chart data for a crypto token' with 'timestamped prices' and returns 'sampled price history with timestamp, price, volume, and market cap' — purely data retrieval with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
Get historical price chart data for a crypto token — timestamped prices for trend analysis. WHEN TO USE: For crypto price history and charting. Use veroq_crypto for current snapshot, this for historical trend. RETURNS: Sampled price history with timestamp, price, volume, and market cap per data point. Includes period change %. COST: 2 credits. EXAMPLE: {. It is categorised as a Read tool in the Veroq MCP Server, which means it retrieves data without modifying state.
Register the Veroq MCP server in PolicyLayer and add a rule for veroq_crypto_chart: 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 Veroq. Nothing to install.
veroq_crypto_chart 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 veroq_crypto_chart 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 veroq_crypto_chart. 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.
veroq_crypto_chart is provided by the Veroq MCP server (veroq-ai/veroq-mcp). 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 →