Get ETF exposure data
AI agents call get_etf_exposure to retrieve information from Unusual Whales MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries ETF exposure data with no side effects. It follows the Read category pattern (get, fetch) common to other sibling tools on this server (get_alerts, get_congress_recent_trades, get_darkpool_ticker, etc.). While the underlying data is financial in nature, the tool itself performs only read-only access.
From the tool's definition Tool name and description indicate data retrieval only: 'Get ETF exposure data' performs a query operation returning financial market information without modifying, executing code, or triggering transactions.
Attacks that exploit this kind of access
Get ETF exposure data. It is categorised as a Read tool in the Unusual Whales MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Unusual Whales MCP Server MCP server in PolicyLayer and add a rule for get_etf_exposure: 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 Unusual Whales MCP Server. Nothing to install.
get_etf_exposure 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_etf_exposure 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_etf_exposure. 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_etf_exposure is provided by the Unusual Whales MCP Server MCP server (phields/unusualwhales-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 →