Generate Golden Lead packets for B2B sales agents. Cross-references SEC filings, GitHub activity, and job postings to score companies as HOT/WARM/COLD leads with AI pivot signals and recommended outreach angles. Use this tool when: - A sales agent needs to prioritise outreach to companies most li...
AI agents call get_b2b_intel 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 synthesizes existing public data (SEC filings, GitHub activity, job postings) to generate intelligence scores and lead rankings. It performs no writes, deletes, code execution, or financial transactions.
From the tool's definition Tool description states it 'Generate[s] Golden Lead packets' by 'Cross-references SEC filings, GitHub activity, and job postings to score companies' and 'Returns per company: lead_score'.
Attacks that exploit this kind of access
Generate Golden Lead packets for B2B sales agents. Cross-references SEC filings, GitHub activity, and job postings to score companies as HOT/WARM/COLD leads with AI pivot signals and recommended outreach angles. Use this tool when: - A sales agent needs to prioritise outreach to companies most likely to buy AI services - You want to detect which companies are actively transitioning to AI and need vendors - A BD agent is building a prospect list with data-backed prioritisation - You need company intelligence that goes beyond basic firmographic data Returns per company: lead_score (HOT/WARM/COLD), ai_pivot_signal, recent_sec_mentions_of_ai, github_ai_repos_added, open_ai_roles, funding_stage, recommended_outreach_angle, key_contacts. Example: getB2bIntel({ companies: [. 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_b2b_intel: 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_b2b_intel 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_b2b_intel 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_b2b_intel. 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_b2b_intel 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 →