"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack...
AI agents call entity_profile to retrieve information from Mcp Openligadb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
type | string | Yes | Entity type. Only "company" supported today; person/place coming soon. |
value | string | Yes | Ticker (e.g., "AAPL") or zero-padded CIK (e.g., "0000320193"). Names not supported — use resolve_entity first if you only have a name. |
Parameters from the server's own tool schema.
This tool gathers and returns information about publicly traded companies from authoritative sources without creating, modifying, or deleting data. It is a pure Read operation.
From the tool's definition Tool description indicates it retrieves and aggregates company profile data across multiple sources (SEC EDGAR, XBRL, USPTO, news, GLEIF) and returns 'cik + company_name; recent_filings; fundamentals.' The verbs are 'Tell me about,' 'research,' 'brief me on,'…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
"Tell me about X" / "research Acme" / "brief me on Tesla" / "what does Apple do" / "company profile for Microsoft" / "give me the rundown on NVDA" / "everything you know about $TICKER" — full cross-source profile of a US public company in ONE parallel call. ALWAYS PREFER over chaining single-pack SEC/XBRL/news lookups when the user asks for a holistic view. Fans out across SEC EDGAR, XBRL, USPTO, news, GLEIF and returns: cik + company_name; recent_filings (up to 5 with pipeworx://edgar/company/{cik}/filings/{accession} URIs); fundamentals (LATEST 10-K Revenues + NetIncomeLoss + Cash, sorted period_end DESC); patents (USPTO PatentsView API sunset May 2025 — soft-fails until reactivated); recent news mentions via GDELT→GNews fallback; LEI via GLEIF. Pass ticker "AAPL" or zero-padded CIK "0000320193" — names not supported (use resolve_entity first if you only have a name). It is categorised as a Read tool in the Mcp Openligadb MCP Server, which means it retrieves data without modifying state.
entity_profile accepts 2 parameters: type, value. Required: type, value. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Openligadb MCP server in PolicyLayer and add a rule for entity_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 Mcp Openligadb. Nothing to install.
entity_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 entity_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 entity_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.
entity_profile is provided by the Mcp Openligadb MCP server (https://gateway.pipeworx.io/openligadb/mcp). 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 →