AI agents call get_exchange_ohlcv to retrieve information from Coin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
OHLCV data retrieval is a standard read operation that queries cryptocurrency market history without modifying, executing external operations, or committing financial transactions. It retrieves historical price and volume data from an exchange, typical of market data APIs. The low severity reflects minimal blast radius if misused—an agent could only retrieve data, not trade or delete.
From the tool's definition Tool name 'get_exchange_ohlcv' indicates data retrieval (OHLCV = Open, High, Low, Close, Volume). The server description emphasizes 'market-data' and 'answer market questions,' and sibling tools like 'get_coin_details', 'get_coin_tickers', and…
Attacks that exploit this kind of access
get_exchange_ohlcv. It is categorised as a Read tool in the Coin MCP Server, which means it retrieves data without modifying state.
Register the Coin MCP server in PolicyLayer and add a rule for get_exchange_ohlcv: 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 Coin. Nothing to install.
get_exchange_ohlcv 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_ohlcv 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_ohlcv. 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_ohlcv is provided by the Coin MCP server (sweetcornna/coin-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 →