获取虚拟币在各交易所的持仓分布 (Coinglass API)
AI agents call get_exchange_position 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 and queries cryptocurrency position data across exchanges—purely informational with no side effects, no code execution, no data modification, and no financial transactions. It aligns with the 'Read' category as a data retrieval operation. Severity is low because misuse would only expose market intelligence data, not enable destructive or financial actions.
From the tool's definition Tool name 'get_exchange_position' and description '获取虚拟币在各交易所的持仓分布' (Get virtual currency position distribution across exchanges) indicates a query operation that retrieves market data.
Attacks that exploit this kind of access
获取虚拟币在各交易所的持仓分布 (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_exchange_position: 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_exchange_position 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_exchange_position 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_exchange_position. 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_exchange_position 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 →