AI agents call list_chains_tvl 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.
This tool retrieves cryptocurrency market data (TVL across chains) without modification, deletion, or execution of arbitrary code. The 'list_' prefix and market-data context confirm a Read operation. Confidence is slightly reduced due to empty description, but the server's purpose and naming conventions provide sufficient context.
From the tool's definition Tool name 'list_chains_tvl' indicates listing/retrieving chain total value locked data. No description provided, but the naming pattern (list_* + TVL metric) and sibling tools like 'get_chain_tvl_history', 'get_coin_details', 'get_coin_tickers' all suggest…
Attacks that exploit this kind of access
list_chains_tvl. 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 list_chains_tvl: 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.
list_chains_tvl 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 list_chains_tvl 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 list_chains_tvl. 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.
list_chains_tvl 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 →