getTokenHistoricalApr

Query product

SERVERBybit MCP Server SOURCEbybit-exchange/trading-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/bybit-exchange-trading-mcp/gettokenhistoricalapr.md

WHAT IT DOES

What getTokenHistoricalApr does on Bybit MCP Server

AI agents call getTokenHistoricalApr to retrieve information from Bybit MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why getTokenHistoricalApr is rated Low

This tool retrieves historical APR data for tokens/products. It performs a query with no side effects, no data modification, no code execution, and no financial transactions. It is purely informational, making it a Read category tool with low severity. Confidence is high based on the clear 'get' and 'query' semantics, though the sparse description limits it slightly.

From the tool's definition Tool name 'getTokenHistoricalApr' and description 'Query product' indicate a data retrieval operation. The 'get' prefix and 'Query' verb are characteristic of read-only operations that retrieve historical APR (Annual Percentage Rate) information without…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs getTokenHistoricalApr safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Bybit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For getTokenHistoricalApr, this is the rule to start with:

getTokenHistoricalApr Allowed

getTokenHistoricalApr is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "getTokenHistoricalApr": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Bybit MCP Server, apply this rule, and every getTokenHistoricalApr call is checked against it from then on.

FAQ

Questions about getTokenHistoricalApr

What does the getTokenHistoricalApr tool do? +

Query product. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getTokenHistoricalApr? +

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

What risk level is getTokenHistoricalApr? +

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

Can I rate-limit getTokenHistoricalApr? +

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

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

getTokenHistoricalApr is provided by the Bybit MCP Server MCP server (bybit-exchange/trading-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Bybit MCP Server, and thousands of servers like it.

This server

All 380 Bybit MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →