Retrieve the component exchanges and trading pairs that make up a Bybit index price,\nincluding their individual weights, current prices, and multipliers.\n\nUse this endpoint when you need to:\n- Understand which exchanges and spot pairs contribute to a Bybit index price\n- Investigate why an in...
AI agents call getIndexPriceComponents to retrieve information from Bybit MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries market data about index price components with no side effects. It is informational only—useful for understanding market structure but cannot execute trades, modify positions, or affect financial obligations. The 'Retrieve' verb and read-only nature clearly categorize it as Read.
From the tool's definition Tool name 'getIndexPriceComponents' and description explicitly states 'Retrieve the component exchanges and trading pairs' with use cases focused on understanding, investigating, and researching index price composition.
Documented attack patterns abuse exactly the kind of access getIndexPriceComponents gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bybit MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getIndexPriceComponents:
{
"version": "1",
"default": "deny",
"tools": {
"getIndexPriceComponents": {}
}
}getIndexPriceComponents is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the component exchanges and trading pairs that make up a Bybit index price,\nincluding their individual weights, current prices, and multipliers.\n\nUse this endpoint when you need to:\n- Understand which exchanges and spot pairs contribute to a Bybit index price\n- Investigate why an index price differs from individual spot market prices\n- Research the composition and weighting methodology of a specific index\n\nReturns. It is categorised as a Read tool in the Bybit MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bybit MCP Server MCP server in PolicyLayer and add a rule for getIndexPriceComponents: 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.
getIndexPriceComponents 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 getIndexPriceComponents 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 getIndexPriceComponents. 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.
getIndexPriceComponents 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.
Start from Bybit 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.
326 Bybit MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.