"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="...
AI agents call compare_entities to retrieve information from Mcp Va Museum 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: "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.
This tool retrieves and queries financial and regulatory data (10-K revenue, net income, FAERS adverse events, FDA approvals) for comparison purposes. It has no side effects—it does not create, modify, delete, or execute arbitrary operations.
From the tool's definition Tool performs side-by-side comparison of entities (companies or drugs) by pulling and retrieving data from SEC EDGAR/XBRL and FDA databases. Verbs used: 'pulls LATEST', 'pulls FAERS adverse-event counts', 'FDA approval counts'.
Attacks that exploit this kind of access
"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. It is categorised as a Read tool in the Mcp Va Museum MCP Server, which means it retrieves data without modifying state.
compare_entities accepts 2 parameters: type, values. Required: type, values. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Va Museum MCP server in PolicyLayer and add a rule for compare_entities: 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 Va Museum. Nothing to install.
compare_entities 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 compare_entities 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 compare_entities. 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.
compare_entities is provided by the Mcp Va Museum MCP server (pipeworx-io/mcp-va-museum). 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 →