Fetch ETF flow and AUM data for BTC, ETH, and Gold spot ETFs.
AI agents call fetch_etf_flows to retrieve information from Market Brief without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical and current ETF flow/AUM metrics from public financial data sources. It performs a read-only query operation with no side effects—no data is created, modified, deleted, or any transactions are executed. While the data pertains to financial markets, the tool itself does not move money, commit financial obligations, or execute trades.
From the tool's definition Tool name 'fetch_etf_flows' and description 'Fetch ETF flow and AUM data' indicate retrieval of financial market data with no modification, deletion, or code execution capabilities.
Attacks that exploit this kind of access
Fetch ETF flow and AUM data for BTC, ETH, and Gold spot ETFs. It is categorised as a Read tool in the Market Brief MCP Server, which means it retrieves data without modifying state.
Register the Market Brief MCP server in PolicyLayer and add a rule for fetch_etf_flows: 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 Market Brief. Nothing to install.
fetch_etf_flows 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 fetch_etf_flows 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 fetch_etf_flows. 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.
fetch_etf_flows is provided by the Market Brief MCP server (yukipanpan/marketbrief). 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 →