获取虚拟币合约的K线数据 (Coinglass API)
AI agents call get_kline_data to retrieve information from Crypto MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves cryptocurrency K-line (candlestick chart) data from Coinglass API. K-line data is read-only historical market information used for technical analysis. It performs no modifications, executions, deletions, or financial transactions. The blast radius of misuse is minimal—an agent could only retrieve unwanted market data, which has no destructive consequences.
From the tool's definition Tool name 'get_kline_data' and description '获取虚拟币合约的K线数据' (retrieve K-line data for virtual currency contracts) indicate data retrieval only. K-line (candlestick) data is historical/technical market information with no side effects.
Attacks that exploit this kind of access
获取虚拟币合约的K线数据 (Coinglass API). It is categorised as a Read tool in the Crypto MCP MCP Server, which means it retrieves data without modifying state.
Register the Crypto MCP server in PolicyLayer and add a rule for get_kline_data: 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 Crypto MCP. Nothing to install.
get_kline_data 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 get_kline_data 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 get_kline_data. 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.
get_kline_data is provided by the Crypto MCP server (kiss-kedaya/crypto_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 →