Get Tinyman analytics data for a specific asset including price, volume, and liquidity.
AI agents call get_asset_analytics to retrieve information from Tinyman 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 and returns analytical metrics about assets on the Tinyman DEX. It performs no state changes, does not execute transactions, and does not move funds. The operation is purely informational retrieval, consistent with the Read category. The low severity reflects that misuse would at worst expose public market data without causing harm.
From the tool's definition Tool description states it retrieves 'analytics data for a specific asset including price, volume, and liquidity' — all read operations with no modification, side effects, or financial transactions.
Attacks that exploit this kind of access
Get Tinyman analytics data for a specific asset including price, volume, and liquidity. It is categorised as a Read tool in the Tinyman MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tinyman MCP Server MCP server in PolicyLayer and add a rule for get_asset_analytics: 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 Tinyman MCP Server. Nothing to install.
get_asset_analytics 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_asset_analytics 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_asset_analytics. 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_asset_analytics is provided by the Tinyman MCP Server MCP server (nautilusoss/tinymanmcp). 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 →