Build a full company intelligence dossier by combining SEC filings + GitHub velocity + hiring signals + patent activity + HackerNews sentiment. Returns a HOT/WARM/COLD lead score with recommended action. Use this tool when: - A sales or BD agent needs a comprehensive one-stop company briefing bef...
AI agents call get_company_profile 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.
Despite the comprehensive nature of the dossier, the tool performs only read operations across multiple public data sources. It queries SEC filings (public records), GitHub metrics (public API), patent databases (public), and sentiment analysis (public content), then synthesizes findings into a lead score. The 'recommended action' is advisory output, not a commitment or execution.
From the tool's definition Tool retrieves and aggregates existing public data sources (SEC filings, GitHub velocity, hiring signals, patent activity, HackerNews sentiment) and returns a lead score with recommended action.
Attacks that exploit this kind of access
Build a full company intelligence dossier by combining SEC filings + GitHub velocity + hiring signals + patent activity + HackerNews sentiment. Returns a HOT/WARM/COLD lead score with recommended action. Use this tool when: - A sales or BD agent needs a comprehensive one-stop company briefing before outreach - An investor agent is doing rapid due diligence on a prospect - You need a 360-degree view of a company. 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_company_profile: 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_company_profile 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_company_profile 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_company_profile. 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_company_profile 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 →