Past 24h trades by token address (requires paid plan)
AI agents call query_coingecko_token_trades to retrieve information from Netmind Web3 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical trading data for a specific token over the past 24 hours. It is a read-only operation that retrieves and displays information without modifying, executing, or deleting anything. The 'requires paid plan' note is a licensing constraint, not a functional capability that changes the risk category.
From the tool's definition Tool name contains 'query' and description states it retrieves 'Past 24h trades by token address' — this is a data retrieval operation with no side effects.
Attacks that exploit this kind of access
Past 24h trades by token address (requires paid plan). It is categorised as a Read tool in the Netmind Web3 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Netmind Web3 MCP Server MCP server in PolicyLayer and add a rule for query_coingecko_token_trades: 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 Netmind Web3 MCP Server. Nothing to install.
query_coingecko_token_trades 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 query_coingecko_token_trades 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 query_coingecko_token_trades. 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.
query_coingecko_token_trades is provided by the Netmind Web3 MCP Server MCP server (protagolabs/netmind-web3-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 →