AI agents call get_chain_tvl_history 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 appears to query historical blockchain TVL metrics, a read-only market data operation. Despite the empty description lowering confidence slightly, the naming pattern and context (cryptocurrency market-data server with sibling tools like get_coin_details, get_coin_tickers) strongly suggest this fetches data without modification or execution. Classified as Read with low severity due to lack of side effects.
From the tool's definition Tool name 'get_chain_tvl_history' indicates retrieval of historical TVL (Total Value Locked) data for blockchain chains. The 'get_' prefix and '_history' suffix are consistent with data retrieval operations. No description provided to confirm side effects.
Attacks that exploit this kind of access
get_chain_tvl_history. 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_chain_tvl_history: 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_chain_tvl_history 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_chain_tvl_history 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_chain_tvl_history. 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_chain_tvl_history 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 →