# compare_entities

"Compare X and Y" / "X vs Y" / "X versus Y" / "which is bigger / better / larger / more profitable" / "rank these companies" / "head to head" — side-by-side comparison of 2–5 companies or drugs in ONE parallel call. ALWAYS PREFER over sequential single-pack lookups when comparing entities. type="company" pulls LATEST 10-K revenue + net income + cash + long-term debt from SEC EDGAR/XBRL (off-calendar fiscal years handled correctly — AAPL Sep, NVDA Jan, etc.). type="drug" pulls FAERS adverse-event counts, FDA approval counts, active trial counts. Results sorted by primary metric so "largest" / "most" / "biggest" reads off the top of the response. Returns paired data + pipeworx:// citation URIs per entity. Replaces 8–15 sequential lookups.

Agent View of the PolicyLayer registry record for `compare_entities`. HTML page: https://policylayer.com/tools/io-github-pipeworx-io-linear/compare-entities

## Facts

- Tool: `compare_entities`
- Server: Linear (`https://gateway.pipeworx.io/linear/mcp`) — https://policylayer.com/tools/io-github-pipeworx-io-linear.md
- Homepage: https://github.com/pipeworx-io/mcp-linear
- Risk category: Read (Low risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: yes
- Parameters: 2 (2 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `type` | string | yes | Entity type: "company" or "drug". |
| `values` | array | yes | For company: 2–5 tickers/CIKs (e.g., ["AAPL","MSFT"]). For drug: 2–5 names (e.g., ["ozempic","mounjaro"]). |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "compare_entities",
    "arguments": {
      "type": "<type>",
      "values": []
    }
  }
}
```

## Why compare_entities is rated Low

This is a read-only tool that retrieves and compares publicly available financial and medical data without altering any state. It poses minimal risk since it cannot create, modify, delete, execute arbitrary code, or move funds. The primary risk is information disclosure or misuse of comparative analysis, which is low severity in a business intelligence context.

From the tool's own definition: "The tool performs side-by-side comparison queries of companies or drugs, pulling financial data from SEC EDGAR/XBRL and adverse-event counts from FAERS/FDA databases."

## Use case

AI agents call compare_entities 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Linear:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "compare_entities": {}
  }
}
```

## Other tools on Linear (35)

- `forget` — Destructive — https://policylayer.com/tools/io-github-pipeworx-io-linear/forget.md
- `generate_llms_txt` — Execute — https://policylayer.com/tools/io-github-pipeworx-io-linear/generate-llms-txt.md
- `polymarket_edges` — Financial — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-edges.md
- `polymarket_fill_risk` — Financial — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-fill-risk.md
- `ai_visibility_check` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/ai-visibility-check.md
- `ask_pipeworx` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/ask-pipeworx.md
- `ask_pipeworx_beta` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/ask-pipeworx-beta.md
- `ask_pipeworx_grounded` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/ask-pipeworx-grounded.md
- `bet_research` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/bet-research.md
- `deep_research` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/deep-research.md
- `discover_tools` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/discover-tools.md
- `entity_profile` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/entity-profile.md
- `linear_get_issue` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-get-issue.md
- `linear_list_issues` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-list-issues.md
- `linear_list_teams` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-list-teams.md
- `linear_search` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/linear-search.md
- `list_subscriptions` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/list-subscriptions.md
- `pipeworx_trending` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/pipeworx-trending.md
- `polymarket_arbitrage` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-arbitrage.md
- `polymarket_edge_tracker` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-edge-tracker.md
- `polymarket_kalshi_spread` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/polymarket-kalshi-spread.md
- `recall` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/recall.md
- `recent_alerts` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/recent-alerts.md
- `recent_changes` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/recent-changes.md
- `resolve_entity` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/resolve-entity.md
- `scan_competitor_ai_presence` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/scan-competitor-ai-presence.md
- `scan_dependency` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/scan-dependency.md
- `search_within` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/search-within.md
- `suggest_questions` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/suggest-questions.md
- `validate_claim` — Read — https://policylayer.com/tools/io-github-pipeworx-io-linear/validate-claim.md
- …and 5 more: https://policylayer.com/tools/io-github-pipeworx-io-linear.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=io-github-pipeworx-io-linear · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/io-github-pipeworx-io-linear