Batch get CEX prices from Coinbase Exchange
AI agents call get_multiple_token_prices to retrieve information from BaseQL MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a read-only operation that queries and retrieves token price data from Coinbase Exchange. There are no side effects, modifications, deletions, or financial transactions involved—it simply fetches market data. The blast radius of misuse is minimal, as price queries cannot harm blockchain data or financial accounts.
From the tool's definition The tool name is 'get_multiple_token_prices' and description states 'Batch get CEX prices from Coinbase Exchange'. This retrieves publicly available pricing data with no ability to modify, delete, or execute operations.
Attacks that exploit this kind of access
Batch get CEX prices from Coinbase Exchange. It is categorised as a Read tool in the BaseQL MCP Server MCP Server, which means it retrieves data without modifying state.
Register the BaseQL MCP Server MCP server in PolicyLayer and add a rule for get_multiple_token_prices: 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 BaseQL MCP Server. Nothing to install.
get_multiple_token_prices 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_multiple_token_prices 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_multiple_token_prices. 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_multiple_token_prices is provided by the BaseQL MCP Server MCP server (jnix2007/baseql-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 →