Fetch private equity (PE) and venture capital (VC) deal flow: funding rounds, exits (IPOs and acquisitions), dry powder levels, sector focus shifts, and notable investor activity. Use this tool when: - A research agent is tracking startup funding trends and investor activity - An agent wants to k...
AI agents call get_private_equity 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 tool retrieves and queries publicly available or market intelligence data about PE/VC deals without any side effects. It performs data retrieval only (search, list, fetch) with no ability to create, modify, delete, or execute operations. The use cases confirm read-only research and analysis functions.
From the tool's definition Tool description indicates 'Fetch private equity (PE) and venture capital (VC) deal flow' with read-only operations: 'funding rounds, exits (IPOs and acquisitions), dry powder levels, sector focus shifts, and notable investor activity.' Returns data fields…
Attacks that exploit this kind of access
Fetch private equity (PE) and venture capital (VC) deal flow: funding rounds, exits (IPOs and acquisitions), dry powder levels, sector focus shifts, and notable investor activity. Use this tool when: - A research agent is tracking startup funding trends and investor activity - An agent wants to know which sectors VCs are currently prioritising - You need to assess private market valuations as a leading indicator for public markets - A BD agent is identifying well-funded startups as potential customers or partners Returns per deal: company, sector, round_type (SEED/A/B/C/GROWTH), amount_usd, lead_investors, valuation_usd, date, country. Also returns: sector_heat_map, top_investors_by_deal_count, dry_powder_estimate. Example: getPrivateEquity({ sector:. 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_private_equity: 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_private_equity 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_private_equity 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_private_equity. 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_private_equity 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 →