Low Risk

crypto_history

Get cryptocurrency historical price data. Args: symbol: Crypto symbol (e.g. BTC, ETH, SOL) start: Start date YYYY-MM-DD (default: 30 days ago) end: End date YYYY-MM-DD (default: today) interval: Time interval - 1D, 1W, 1M (default: 1D)

How to control crypto_history ↓

What crypto_history does on VNStock Agent MCP Server

AI agents call crypto_history to retrieve information from VNStock Agent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why crypto_history needs a policy

This tool retrieves historical price data for cryptocurrencies. It is a read-only query with no side effects, no data modification, and no financial transactions. It simply fetches market data based on symbol, date range, and interval parameters.

From the tool's definition Get cryptocurrency historical price data

Documented attack patterns abuse exactly the kind of access crypto_history gives an agent:

How to control crypto_history

PolicyLayer is an MCP gateway — it sits between your AI agents and VNStock Agent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for crypto_history:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "crypto_history": {}
  }
}

crypto_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register VNStock Agent MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about crypto_history

What does the crypto_history tool do? +

Get cryptocurrency historical price data. Args: symbol: Crypto symbol (e.g. BTC, ETH, SOL) start: Start date YYYY-MM-DD (default: 30 days ago) end: End date YYYY-MM-DD (default: today) interval: Time interval - 1D, 1W, 1M (default: 1D). It is categorised as a Read tool in the VNStock Agent MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on crypto_history? +

Register the VNStock Agent MCP Server MCP server in PolicyLayer and add a rule for crypto_history: 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 VNStock Agent MCP Server. Nothing to install.

What risk level is crypto_history? +

crypto_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit crypto_history? +

Yes. Add a rate_limit block to the crypto_history 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.

How do I block crypto_history completely? +

Set action: deny in the PolicyLayer policy for crypto_history. 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.

What MCP server provides crypto_history? +

crypto_history is provided by the VNStock Agent MCP Server MCP server (mrgoonie/vnstock-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every VNStock Agent MCP Server tool call.

Start from VNStock Agent MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

21 VNStock Agent MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.