Get historical earnings data for a ticker
AI agents call get_earnings_ticker 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 queries and retrieves historical earnings information for a given ticker symbol. It performs a read-only operation that retrieves data from the Unusual Whales API without creating, modifying, deleting, or executing code. The action is a simple data fetch with no capability to change system state or trigger external operations.
From the tool's definition Tool name 'get_earnings_ticker' and description 'Get historical earnings data for a ticker' indicate retrieval of earnings data without modification or side effects.
Attacks that exploit this kind of access
Get historical earnings data for a ticker. 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_earnings_ticker: 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_earnings_ticker 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_earnings_ticker 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_earnings_ticker. 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_earnings_ticker 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 →