resolve_entity
"What's the ticker for…" / "find the CIK for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" — resolve a user-spoken NAME to the canonical/official identifier other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: ...
This record as markdown: /tools/io-github-pipeworx-io-linear/resolve-entity.md
What resolve_entity does on Linear
AI agents call resolve_entity 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: "company" or "drug". |
value | string | Yes | For company: ticker (AAPL), CIK (0000320193), or name. For drug: brand or generic name (e.g., "ozempic", "metformin"). |
Parameters from the server's own tool schema.
Why resolve_entity is rated Low
The tool resolves names to canonical IDs by querying external registries (SEC EDGAR, RxNorm). It retrieves and returns identifiers without creating, modifying, or deleting any data. This is a pure read/lookup operation with minimal blast radius.
From the tool's definition "resolve a user-spoken NAME to the canonical/official identifier" — looks up identifiers from SEC EDGAR, RxNorm, and similar registries; purely a lookup/query operation with no side effects
Attacks that exploit this kind of access
The rule that runs resolve_entity 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 resolve_entity, this is the rule to start with:
resolve_entity is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Linear, apply this rule, and every resolve_entity call is checked against it from then on.
Questions about resolve_entity
"What's the ticker for…" / "find the CIK for…" / "what's the RxCUI for…" / "look up the ID for…" / "what is X's official identifier" — resolve a user-spoken NAME to the canonical/official identifier other tools require as input. Use FIRST whenever you have a name but need an ID. SUPPORTED TYPES: "company" (returns ticker + 10-digit CIK + company_name from SEC EDGAR + pipeworx://edgar/company/{cik} citation URI; accepts ticker, CIK, or company name as input — auto-disambiguated), "drug" (returns RxCUI + ingredient + brand from RxNorm + pipeworx://rxnorm/{rxcui} citation; accepts brand or generic name). Each call cascades through several lookup endpoints internally — using resolve_entity replaces 2-3 manual lookups. It is categorised as a Read tool in the Linear MCP Server, which means it retrieves data without modifying state.
resolve_entity 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 Linear MCP server in PolicyLayer and add a rule for resolve_entity: 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.
resolve_entity 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 resolve_entity 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 resolve_entity. 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.
resolve_entity 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.
More on Linear, and thousands of servers like it.
This server
Across the catalogue