Low Risk

defi_get_token_price_history

Get historical price for a token at a specific timestamp.

How to control defi_get_token_price_history ↓

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

Low Risk

This tool queries and returns existing price history data without side effects. It does not create, modify, delete, or execute any financial transactions. While it operates in a financial context (DeFi), it only reads data and does not move money or commit financial obligations, making it a Read category risk with low severity.

From the tool's definition Tool retrieves historical price data for a token at a specific timestamp. The verb 'get' and phrase 'historical price' indicate data retrieval with no modification, deletion, or execution of transactions.

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

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

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

defi_get_token_price_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 BNB Chain MCP — 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.

Go deeper

What does the defi_get_token_price_history tool do? +

Get historical price for a token at a specific timestamp. It is categorised as a Read tool in the BNB Chain MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on defi_get_token_price_history? +

Register the BNB Chain MCP server in PolicyLayer and add a rule for defi_get_token_price_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 BNB Chain MCP. Nothing to install.

What risk level is defi_get_token_price_history? +

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

Can I rate-limit defi_get_token_price_history? +

Yes. Add a rate_limit block to the defi_get_token_price_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 defi_get_token_price_history completely? +

Set action: deny in the PolicyLayer policy for defi_get_token_price_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 defi_get_token_price_history? +

defi_get_token_price_history is provided by the BNB Chain MCP server (nirholas/bnbchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every BNB Chain MCP tool call.

Deterministic rules across all 1240 BNB Chain MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

1240 BNB Chain MCP tools catalogued and risk-classified — across an index of 42,500+ 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.