Get market tide data
AI agents call get_market_tide 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 market data without modifying, executing operations, or causing financial transactions. The 'get_' prefix and passive data retrieval nature place it firmly in the Read category. Severity is low because unauthorized access to market data, while potentially valuable to competitors, does not directly damage systems, destroy data, or commit financial obligations.
From the tool's definition Tool name 'get_market_tide' and description 'Get market tide data' indicate a retrieval operation. The verb 'get' combined with the server's stated purpose of providing 'real-time financial data' and 'market intelligence' confirms this is a data-fetching tool…
Attacks that exploit this kind of access
Get market tide 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_market_tide: 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_market_tide 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_market_tide 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_market_tide. 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_market_tide 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 →