entity_profile

SERVERLinear SOURCEhttps://gateway.pipeworx.io/linear/mcp

Low RISK CLASS

Category Read

Parameters 22 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pipeworx-io-linear/entity-profile.md

WHAT IT DOES

What entity_profile does on Linear

AI agents call entity_profile to retrieve information from Linear without modifying anything. It is 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.

RISK

Why entity_profile is rated Low

entity_profile queries and retrieves public company information from multiple data sources (SEC filings, news, patent records, etc.) without modifying any data or executing code. It is purely informational, aggregating read-only lookups into a holistic view. The tool has no side effects, no code execution risk, and no destructive capability.

From the tool's definition Tool description emphasizes retrieval and aggregation: 'full cross-source profile', 'fans out across SEC EDGAR, XBRL, USPTO, news, GLEIF and returns' company data, fundamentals, and filings.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs entity_profile safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Linear, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For entity_profile, this is the rule to start with:

entity_profile Allowed

entity_profile is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "entity_profile": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every entity_profile call is checked against it from then on.

FAQ

Questions about entity_profile

What does the entity_profile tool do? +

"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 Linear MCP Server, which means it retrieves data without modifying state.

What parameters does entity_profile accept? +

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.

How do I enforce a policy on entity_profile? +

Register the Linear 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 Linear. Nothing to install.

What risk level is entity_profile? +

entity_profile is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit entity_profile? +

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.

How do I block entity_profile completely? +

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.

What MCP server provides entity_profile? +

entity_profile is provided by the Linear MCP server (https://gateway.pipeworx.io/linear/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Linear, and thousands of servers like it.

This server

All 36 Linear tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →