Fetch upcoming and recent earnings reports for US public companies: EPS estimates vs actuals, revenue beats/misses, guidance changes, and a BEAT/MISS/IN-LINE signal. Use this tool when: - A trading agent needs to know which stocks are reporting earnings and when - You want to identify earnings su...
AI agents call get_earnings to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation—it retrieves financial data without side effects. Severity is medium rather than low because earnings data is market-sensitive and time-critical; misuse by an unprompted agent could lead to unintended trading decisions or information leakage of material non-public earnings surprises if the tool has access to pre-release data.
From the tool's definition Tool fetches earnings reports, EPS estimates vs actuals, revenue data, and beat/miss signals. Description explicitly states 'Fetch' and all use cases are retrieval-oriented: 'needs to know', 'identify', 'building an earnings calendar'.
Attacks that exploit this kind of access
Fetch upcoming and recent earnings reports for US public companies: EPS estimates vs actuals, revenue beats/misses, guidance changes, and a BEAT/MISS/IN-LINE signal. Use this tool when: - A trading agent needs to know which stocks are reporting earnings and when - You want to identify earnings surprises that could cause price gaps - A portfolio agent needs to reduce risk before a major earnings event - An analyst agent is building an earnings calendar for the week Returns per company: ticker, company_name, report_date, EPS_estimate, EPS_actual, EPS_surprise_pct, revenue_estimate, revenue_actual, signal (BEAT/MISS/IN-LINE), guidance (RAISED/LOWERED/MAINTAINED). Example: getEarnings({ days: 7, symbols:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_earnings: 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 Omni Service Node. Nothing to install.
get_earnings 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 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. 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 is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). 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 →