Track merger and acquisition (M&A) activity: announced deals, rumoured targets (based on options activity and news signals), deal premiums, regulatory status, and sector consolidation trends. Use this tool when: - A trading agent wants to identify potential M&A targets for event-driven trades - A...
AI agents call get_merger_activity 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 M&A data and signals without creating, modifying, executing, or deleting anything. It is fundamentally a Read operation. Severity is medium rather than low because the data (rumored acquisition targets, deal premiums, regulatory signals) could enable event-driven trading strategies that have material financial impact if misused by an AI agent, but the tool itself performs no financial…
From the tool's definition Tool description states it 'Track[s] merger and acquisition (M&A) activity: announced deals, rumoured targets...
Attacks that exploit this kind of access
Track merger and acquisition (M&A) activity: announced deals, rumoured targets (based on options activity and news signals), deal premiums, regulatory status, and sector consolidation trends. Use this tool when: - A trading agent wants to identify potential M&A targets for event-driven trades - A research agent is building a sector consolidation thesis - You need to know about pending regulatory approvals for major deals - An agent is assessing whether a company is an acquisition target or acquirer Returns per deal: acquirer, target, deal_value_usd, premium_pct, sector, status (RUMOURED/ANNOUNCED/PENDING_REGULATORY/CLOSED/WITHDRAWN), regulatory_risk, synergy_rationale. Example: getMergerActivity({ 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_merger_activity: 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_merger_activity 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_merger_activity 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_merger_activity. 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_merger_activity 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 →