Gets current prices for multiple tokens from CoinGecko.
AI agents call get_multiple_token_prices to retrieve information from SEI MCP Server V2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries public token price data from an external source (CoinGecko) and returns the information without modifying any state, executing code, or committing financial transactions. It is a straightforward read operation with minimal risk even if misused, as price data is public and cannot cause harm through retrieval alone.
From the tool's definition Tool description states it 'Gets current prices for multiple tokens from CoinGecko' — a pure data retrieval operation with no write, execution, or financial side effects.
Attacks that exploit this kind of access
Gets current prices for multiple tokens from CoinGecko. It is categorised as a Read tool in the SEI MCP Server V2 MCP Server, which means it retrieves data without modifying state.
Register the SEI MCP Server V2 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 SEI MCP Server V2. 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 SEI MCP Server V2 MCP server (testinguser1111111/sei-mcp-server). 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 →