Get asset volume, swaps, total lockup, vwap and confidence history
AI agents call api_vestige_view_asset_history to retrieve information from Algorand MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves blockchain asset history metrics without side effects. It is purely informational, making it a Read category risk with low severity—harmless for an AI agent to invoke even with untrusted arguments, as it cannot alter state or trigger operations.
From the tool's definition Tool retrieves historical data ('asset volume, swaps, total lockup, vwap and confidence history'); no modification, deletion, or execution indicated. The verb 'view' and absence of write/execute descriptors confirm read-only access.
Documented attack patterns abuse exactly the kind of access api_vestige_view_asset_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Algorand MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for api_vestige_view_asset_history:
{
"version": "1",
"default": "deny",
"tools": {
"api_vestige_view_asset_history": {}
}
} api_vestige_view_asset_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get asset volume, swaps, total lockup, vwap and confidence history. It is categorised as a Read tool in the Algorand MCP MCP Server, which means it retrieves data without modifying state.
Register the Algorand MCP server in PolicyLayer and add a rule for api_vestige_view_asset_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 Algorand MCP. Nothing to install.
api_vestige_view_asset_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 api_vestige_view_asset_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 api_vestige_view_asset_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.
api_vestige_view_asset_history is provided by the Algorand MCP server (goplausible/algorand-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Algorand MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
172 Algorand MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.