AI agents call get_consolidated_orderbook 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.
The tool retrieves cryptocurrency orderbook data without modifying or executing operations. No side effects are indicated. Though the description is empty, the naming convention and server context strongly suggest this is a read-only data retrieval operation. Severity is low because orderbook data access has minimal blast radius—it cannot alter market state, execute transactions, or cause financial harm.
From the tool's definition Tool name 'get_consolidated_orderbook' follows the 'get_' prefix pattern consistent with other data retrieval tools on this server (get_aggregated_ohlc, get_chain_tvl_history, get_coin_details, get_coin_tickers).
Attacks that exploit this kind of access
get_consolidated_orderbook. 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_consolidated_orderbook: 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_consolidated_orderbook 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_consolidated_orderbook 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_consolidated_orderbook. 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_consolidated_orderbook 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 →