get_tvl_history

Get historical TVL (Total Value Locked) data. Can filter by chain and specify time period.

Server RWA Pipe MCP Server rwapipe/mcp
Category Read
Risk class Low
Parameters 00 required

What get_tvl_history does on RWA Pipe MCP Server

AI agents call get_tvl_history to retrieve information from RWA Pipe MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_tvl_history needs a policy

This tool retrieves and queries historical financial analytics data (TVL metrics) from RWA blockchain assets without creating, modifying, deleting, or executing any operations. It is a straightforward data access function that returns time-series information, consistent with the 'Read' category. The lack of side effects, inability to affect asset state, and purely informational nature result in low severity.

From the tool's definition Tool name 'get_tvl_history' and description 'Get historical TVL (Total Value Locked) data. Can filter by chain and specify time period' indicate pure data retrieval with no modification, deletion, or execution capabilities.

Questions about get_tvl_history

What does the get_tvl_history tool do? +

Get historical TVL (Total Value Locked) data. Can filter by chain and specify time period. It is categorised as a Read tool in the RWA Pipe MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tvl_history? +

Register the RWA Pipe MCP Server MCP server in PolicyLayer and add a rule for get_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 RWA Pipe MCP Server. Nothing to install.

What risk level is get_tvl_history? +

get_tvl_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tvl_history? +

Yes. Add a rate_limit block to the get_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.

How do I block get_tvl_history completely? +

Set action: deny in the PolicyLayer policy for get_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.

What MCP server provides get_tvl_history? +

get_tvl_history is provided by the RWA Pipe MCP Server MCP server (rwapipe/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.