Fetch upcoming and recently priced IPOs with deal size, pricing range, market cap, sector, and underwriter details. Use this tool when: - A trading agent wants to participate in or monitor upcoming IPOs - A research agent is assessing new public company supply hitting the market - You need to kno...
AI agents call get_ipo_calendar 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-only query tool that retrieves informational data about IPOs. While the data has financial relevance, the tool itself does not execute trades, transfer funds, or modify any state. An AI agent misusing this tool could only gather market intelligence; it cannot commit financial obligations or execute transactions.
From the tool's definition Tool name 'get_ipo_calendar' and description 'Fetch upcoming and recently priced IPOs' with fields like pricing_date, shares_offered, price_range, market_cap, sector, underwriter.
Attacks that exploit this kind of access
Fetch upcoming and recently priced IPOs with deal size, pricing range, market cap, sector, and underwriter details. Use this tool when: - A trading agent wants to participate in or monitor upcoming IPOs - A research agent is assessing new public company supply hitting the market - You need to know which sectors are attracting new listings - An agent wants to assess market risk appetite via IPO activity (hot IPO market = RISK_ON) Returns per IPO: company_name, ticker, exchange, pricing_date, shares_offered, price_range_low/high, expected_market_cap, sector, lead_underwriter, status (UPCOMING/PRICED/WITHDRAWN). Example: getIpoCalendar({ days: 14 }) → 3 upcoming IPOs next 2 weeks: $2.1B fintech, $800M biotech, $450M SaaS. Cost: $0.005 USDC per call. 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_ipo_calendar: 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_ipo_calendar 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_ipo_calendar 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_ipo_calendar. 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_ipo_calendar 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 →